[jira] [Assigned] (MESOS-1272) Show logos on the 'Powered By' page.
[ https://issues.apache.org/jira/browse/MESOS-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester reassigned MESOS-1272: -- Assignee: Dave Lester > Show logos on the 'Powered By' page. > > > Key: MESOS-1272 > URL: https://issues.apache.org/jira/browse/MESOS-1272 > Project: Mesos > Issue Type: Improvement > Components: project website >Reporter: Benjamin Mahler >Assignee: Dave Lester > > Would be awesome to see a composition of logos here in addition to the > bulleted list: http://mesos.apache.org/documentation/latest/powered-by-mesos/ -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1508) Broken Links in Web Farm Documentation
[ https://issues.apache.org/jira/browse/MESOS-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14036330#comment-14036330 ] Dave Lester commented on MESOS-1508: +1 to removing this; PR are welcome. Would also love to see someone create a more-generic documentation page about running Mesos on EC2. > Broken Links in Web Farm Documentation > -- > > Key: MESOS-1508 > URL: https://issues.apache.org/jira/browse/MESOS-1508 > Project: Mesos > Issue Type: Documentation > Components: documentation >Affects Versions: 0.18.0 >Reporter: Ken Sipe >Priority: Minor > Labels: documentation > Original Estimate: 1h > Remaining Estimate: 1h > > the documentation at > http://mesos.apache.org/documentation/running-a-web-application-farm-on-mesos/ > has the following issues: > 1. the link for "Animoto blog post about adding/removing servers to haproxy" > is great if you are looking for pictures... not so great if you are looking > for anything to do with haproxy. > 2. the link for "andyk-elb+apache-notorque" is a development branch which > 404s. Checking for remote branches shows this branch doesn't exist. > I would send a PR with fixes... however it is unclear how to change this > document to be correct. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1508) Broken Links in Web Farm Documentation
[ https://issues.apache.org/jira/browse/MESOS-1508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14036313#comment-14036313 ] Dave Lester commented on MESOS-1508: The Apache source repo is mirrored on GH: https://github.com/apache/mesos -- you'll see the relevant document in the /docs/ folder, running-a-web-application-farm-on-mesos.md. You can fork the Apache repo, make changes, and send a PR. IMHO, this particular documentation should be rewritten, or removed entirely -- it's more than 12 months old, and a reference to it was removed from the home.md file (which essentially serves as the index for the docs) long ago. > Broken Links in Web Farm Documentation > -- > > Key: MESOS-1508 > URL: https://issues.apache.org/jira/browse/MESOS-1508 > Project: Mesos > Issue Type: Documentation > Components: documentation >Affects Versions: 0.18.0 >Reporter: Ken Sipe >Priority: Minor > Labels: documentation > Original Estimate: 1h > Remaining Estimate: 1h > > the documentation at > http://mesos.apache.org/documentation/running-a-web-application-farm-on-mesos/ > has the following issues: > 1. the link for "Animoto blog post about adding/removing servers to haproxy" > is great if you are looking for pictures... not so great if you are looking > for anything to do with haproxy. > 2. the link for "andyk-elb+apache-notorque" is a development branch which > 404s. Checking for remote branches shows this branch doesn't exist. > I would send a PR with fixes... however it is unclear how to change this > document to be correct. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (MESOS-1309) Automate updating the website for a new release
[ https://issues.apache.org/jira/browse/MESOS-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033343#comment-14033343 ] Dave Lester edited comment on MESOS-1309 at 6/17/14 2:49 AM: - [~vinodkone] We can't automate writing the actual posts, but we should be able to update the website automatically whether or not a blog post has been published at the same time. MESOS-1495 will give us the flexibility to do that. was (Author: davelester): [~vinodkone] Blog posts are written by humans, not algorithms, so we can't automate that. We should be able to update the website automatically though, whether or not a blog post has been published at the same time; MESOS-1495 will give us the flexibility to do that. > Automate updating the website for a new release > --- > > Key: MESOS-1309 > URL: https://issues.apache.org/jira/browse/MESOS-1309 > Project: Mesos > Issue Type: Improvement > Components: project website >Reporter: Vinod Kone >Priority: Minor > > This could be script that lives in our website repo that > 1) updates the links in the website to the latest release which appear on the > homepage and downloads page > 2) deletes old release from dist.a.o per MESOS-850 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1309) Automate updating the website for a new release
[ https://issues.apache.org/jira/browse/MESOS-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033343#comment-14033343 ] Dave Lester commented on MESOS-1309: [~vinodkone] Blog posts are written by humans, not algorithms, so we can't automate that. We should be able to update the website automatically though, whether or not a blog post has been published at the same time; MESOS-1495 will give us the flexibility to do that. > Automate updating the website for a new release > --- > > Key: MESOS-1309 > URL: https://issues.apache.org/jira/browse/MESOS-1309 > Project: Mesos > Issue Type: Improvement > Components: project website >Reporter: Vinod Kone >Priority: Minor > > This could be script that lives in our website repo that > 1) updates the links in the website to the latest release which appear on the > homepage and downloads page > 2) deletes old release from dist.a.o per MESOS-850 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1309) Automate updating the website for a new release
[ https://issues.apache.org/jira/browse/MESOS-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester updated MESOS-1309: --- Description: This could be script that lives in our website repo that 1) updates the links in the website to the latest release which appear on the homepage and downloads page 2) deletes old release from dist.a.o per MESOS-850 was: This could be script that lives in our website repo that 1) updates the links in the website to the latest release which appear on the homepage and downloads page 2) deletes old release from dist.a.o per MESOS-850 3) Drafts a release announcement > Automate updating the website for a new release > --- > > Key: MESOS-1309 > URL: https://issues.apache.org/jira/browse/MESOS-1309 > Project: Mesos > Issue Type: Improvement > Components: project website >Reporter: Vinod Kone >Priority: Minor > > This could be script that lives in our website repo that > 1) updates the links in the website to the latest release which appear on the > homepage and downloads page > 2) deletes old release from dist.a.o per MESOS-850 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (MESOS-1495) Create separate local data file to manage releases
Dave Lester created MESOS-1495: -- Summary: Create separate local data file to manage releases Key: MESOS-1495 URL: https://issues.apache.org/jira/browse/MESOS-1495 Project: Mesos Issue Type: Technical task Components: project website Reporter: Dave Lester Currently, release info is managed in multiple places on the website. This ticket is to create and manage a local data file which contains a release number, link to release notes, and an optional blog post so that we can dynamically display (incl adding and removing) releases from the website by editing a single file. Looks like we can achieve this with Middleman by creating a separate YAML file: http://middlemanapp.com/advanced/local-data/, perhaps /releases.yml? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1309) Automate updating the website for a new release
[ https://issues.apache.org/jira/browse/MESOS-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14033311#comment-14033311 ] Dave Lester commented on MESOS-1309: [~vinodkone] I agree that we should automate sending the release announcement to the best of our ability, but IMHO that shouldn't be part of the website repo but instead part of /support/release.sh. What's your opinion? > Automate updating the website for a new release > --- > > Key: MESOS-1309 > URL: https://issues.apache.org/jira/browse/MESOS-1309 > Project: Mesos > Issue Type: Improvement > Components: project website >Reporter: Vinod Kone >Priority: Minor > > This could be script that lives in our website repo that > 1) updates the links in the website to the latest release which appear on the > homepage and downloads page > 2) deletes old release from dist.a.o per MESOS-850 > 3) Drafts a release announcement -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1309) Automate updating the website for a new release
[ https://issues.apache.org/jira/browse/MESOS-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester updated MESOS-1309: --- Description: This could be script that lives in our website repo that 1) updates the links in the website to the latest release which appear on the homepage and downloads page 2) deletes old release from dist.a.o per MESOS-850 3) Drafts a release announcement was: This could be script that lives in our website repo that 1) updates the links in the website to the latest release 2) deletes old release from dist.a.o per MESOS-850 3) Drafts a release announcement > Automate updating the website for a new release > --- > > Key: MESOS-1309 > URL: https://issues.apache.org/jira/browse/MESOS-1309 > Project: Mesos > Issue Type: Improvement > Components: project website >Reporter: Vinod Kone >Priority: Minor > > This could be script that lives in our website repo that > 1) updates the links in the website to the latest release which appear on the > homepage and downloads page > 2) deletes old release from dist.a.o per MESOS-850 > 3) Drafts a release announcement -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (MESOS-1494) Display dynamic list of recent blog posts on website
Dave Lester created MESOS-1494: -- Summary: Display dynamic list of recent blog posts on website Key: MESOS-1494 URL: https://issues.apache.org/jira/browse/MESOS-1494 Project: Mesos Issue Type: Technical task Components: project website Reporter: Dave Lester Priority: Minor We should create an automated solution that will update this list when there are new posts added. Currently, the homepage list of recent blog posts is manually updated. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (MESOS-1493) Add RSS feed to the Mesos blog
Dave Lester created MESOS-1493: -- Summary: Add RSS feed to the Mesos blog Key: MESOS-1493 URL: https://issues.apache.org/jira/browse/MESOS-1493 Project: Mesos Issue Type: Task Components: project website Reporter: Dave Lester Priority: Minor The Mesos website have a dedicated page to view all recent blog posts http://mesos.apache.org/blog/, but we're not generating RSS/atom feeds for those same posts. We should add an RSS feed, and clearly link to the feed so folks can subscribe to it. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1478) Replace Master/Slave terminology
[ https://issues.apache.org/jira/browse/MESOS-1478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14030189#comment-14030189 ] Dave Lester commented on MESOS-1478: [~clarkbreyman], thank you for suggesting this change. I agree that it's one that should be made. +1 to [~adam-mesos]'s suggestion of using coordinator/supervisor and worker as alternate terminology. > Replace Master/Slave terminology > > > Key: MESOS-1478 > URL: https://issues.apache.org/jira/browse/MESOS-1478 > Project: Mesos > Issue Type: Improvement >Reporter: Clark Breyman >Priority: Minor > > Inspired by the comments on this PR: > https://github.com/django/django/pull/2692 > TL;DR - Computers sharing work should be a good thing. Using the language of > human bondage and suffering is inappropriate in this context. It also has the > potential to alienate users and community members. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1272) Show logos on the 'Powered By' page.
[ https://issues.apache.org/jira/browse/MESOS-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13986293#comment-13986293 ] Dave Lester commented on MESOS-1272: +1! The only hangup is that standard markdown format doesn't support tables. I believe there are some markdown extensions that we could adopt to achieve this, but we'll need to make sure that any markdown extension is compatible with the markdown rendering of our static site generator. > Show logos on the 'Powered By' page. > > > Key: MESOS-1272 > URL: https://issues.apache.org/jira/browse/MESOS-1272 > Project: Mesos > Issue Type: Improvement > Components: project website >Reporter: Benjamin Mahler > > Would be awesome to see a composition of logos here in addition to the > bulleted list: http://mesos.apache.org/documentation/latest/powered-by-mesos/ -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-649) Establish Mesos blog planet
[ https://issues.apache.org/jira/browse/MESOS-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984055#comment-13984055 ] Dave Lester commented on MESOS-649: --- I've created INFRA-7641 to track the installation of a Mesos blog planet. As I discussed in my email to the dev list, I believe an unfiltered feed of Mesos blogs will provide a real-time way to stay on top of the project, encourage community participation, and scale without requiring the same editorial control we use when updating the Apache Mesos website. > Establish Mesos blog planet > --- > > Key: MESOS-649 > URL: https://issues.apache.org/jira/browse/MESOS-649 > Project: Mesos > Issue Type: Task >Reporter: Dave Lester >Assignee: Dave Lester >Priority: Minor > > Establish a Mesos blog planet to create a feed of posts and blogs about > Mesos. This was discussed on the Mesos dev mailing list, with regard to a > process for featuring blog posts on the website: > http://markmail.org/message/jpj4sci3hciqp2px -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-649) Establish Mesos blog planet
[ https://issues.apache.org/jira/browse/MESOS-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester updated MESOS-649: -- Description: Establish a Mesos blog planet to create a feed of posts and blogs about Mesos. This was discussed on the Mesos dev mailing list, with regard to a process for featuring blog posts on the website: http://markmail.org/message/jpj4sci3hciqp2px (was: Before I create an INFRA ticket to help set one up, what do folks think about creating a blog planet for Mesos? I'm not sure many of us are currently blogging, but it would be a good way to get the word out about the project and encourage more community participation. Additionally, any suggestions for who we would include? Any volunteers?) > Establish Mesos blog planet > --- > > Key: MESOS-649 > URL: https://issues.apache.org/jira/browse/MESOS-649 > Project: Mesos > Issue Type: Task >Reporter: Dave Lester >Assignee: Dave Lester >Priority: Minor > > Establish a Mesos blog planet to create a feed of posts and blogs about > Mesos. This was discussed on the Mesos dev mailing list, with regard to a > process for featuring blog posts on the website: > http://markmail.org/message/jpj4sci3hciqp2px -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-649) Establish Mesos blog planet
[ https://issues.apache.org/jira/browse/MESOS-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester updated MESOS-649: -- Summary: Establish Mesos blog planet (was: Create Mesos blog planet?) > Establish Mesos blog planet > --- > > Key: MESOS-649 > URL: https://issues.apache.org/jira/browse/MESOS-649 > Project: Mesos > Issue Type: Task >Reporter: Dave Lester >Assignee: Dave Lester >Priority: Minor > > Before I create an INFRA ticket to help set one up, what do folks think about > creating a blog planet for Mesos? I'm not sure many of us are currently > blogging, but it would be a good way to get the word out about the project > and encourage more community participation. > Additionally, any suggestions for who we would include? Any volunteers? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (MESOS-1245) MesosCon Program
Dave Lester created MESOS-1245: -- Summary: MesosCon Program Key: MESOS-1245 URL: https://issues.apache.org/jira/browse/MESOS-1245 Project: Mesos Issue Type: Sub-task Reporter: Dave Lester Assignee: Dave Lester Finalize schedule and program of speakers for MesosCon. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1244) Recruit MesosCon sponsors
[ https://issues.apache.org/jira/browse/MESOS-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980332#comment-13980332 ] Dave Lester commented on MESOS-1244: Currently confirmed Platinum Sponsors: Twitter Mesosphere > Recruit MesosCon sponsors > - > > Key: MESOS-1244 > URL: https://issues.apache.org/jira/browse/MESOS-1244 > Project: Mesos > Issue Type: Sub-task >Reporter: Dave Lester >Assignee: Dave Lester > Labels: Conference, MesosCon > > http://events.linuxfoundation.org/events/mesoscon/sponsor/become-a-sponsor > Platinum level ($10k), and Gold level ($5k) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (MESOS-1244) Recruit MesosCon sponsors
Dave Lester created MESOS-1244: -- Summary: Recruit MesosCon sponsors Key: MESOS-1244 URL: https://issues.apache.org/jira/browse/MESOS-1244 Project: Mesos Issue Type: Sub-task Reporter: Dave Lester Assignee: Dave Lester http://events.linuxfoundation.org/events/mesoscon/sponsor/become-a-sponsor Platinum level ($10k), and Gold level ($5k) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1166) Planning MesosCon
[ https://issues.apache.org/jira/browse/MESOS-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester updated MESOS-1166: --- Description: MesosCon is the first-ever Apache Mesos Conference. MesosCon 2014 is being co-organized with the Linux Foundation, who is helping with registration and logistics for the event. Basic Event Details: August 21, 2014 Chicago, IL One day event, focused on Apache Mesos and its ecosystem. Event website: http://events.linuxfoundation.org/events/mesoscon Call for Proposals (Due 5/16): http://events.linuxfoundation.org/events/mesoscon/program/cfp This event has been approved by the Mesos PMC and Apache Brand Management committee. was: August 21, 2014 Chicago, IL One day event, focused on Apache Mesos and its ecosystem. Morning will likely include a workshop. This event has been approved by the Mesos PMC and Apache Brand Management committee. > Planning MesosCon > - > > Key: MESOS-1166 > URL: https://issues.apache.org/jira/browse/MESOS-1166 > Project: Mesos > Issue Type: Task >Reporter: Dave Lester >Assignee: Dave Lester > Labels: Conference, MesosCon > > MesosCon is the first-ever Apache Mesos Conference. MesosCon 2014 is being > co-organized with the Linux Foundation, who is helping with registration and > logistics for the event. > Basic Event Details: > August 21, 2014 > Chicago, IL > One day event, focused on Apache Mesos and its ecosystem. > Event website: > http://events.linuxfoundation.org/events/mesoscon > Call for Proposals (Due 5/16): > http://events.linuxfoundation.org/events/mesoscon/program/cfp > This event has been approved by the Mesos PMC and Apache Brand Management > committee. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1166) Planning MesosCon
[ https://issues.apache.org/jira/browse/MESOS-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester updated MESOS-1166: --- Description: August 21, 2014 Chicago, IL One day event, focused on Apache Mesos and its ecosystem. Morning will likely include a workshop. This event has been approved by the Mesos PMC and Apache Brand Management committee. was: An official announcement will follow, including attendee registration and CFP. In the meantime, here are some additional details. Save the date! August 21, 2014 Chicago, IL One day event, focused on Apache Mesos and its ecosystem. Morning will likely include a workshop. This event has been approved by the Mesos PMC and Apache Brand Management committee. > Planning MesosCon > - > > Key: MESOS-1166 > URL: https://issues.apache.org/jira/browse/MESOS-1166 > Project: Mesos > Issue Type: Task >Reporter: Dave Lester >Assignee: Dave Lester > Labels: Conference, MesosCon > > August 21, 2014 > Chicago, IL > One day event, focused on Apache Mesos and its ecosystem. Morning will likely > include a workshop. > This event has been approved by the Mesos PMC and Apache Brand Management > committee. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1166) Planning MesosCon
[ https://issues.apache.org/jira/browse/MESOS-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13980308#comment-13980308 ] Dave Lester commented on MESOS-1166: [~ijimenez] Thanks for volunteering, I'll get in touch about the program committee. I'll also add a few sub-tasks to this larger Planning MesosCon issue to track our progress with sponsors, the program, etc. > Planning MesosCon > - > > Key: MESOS-1166 > URL: https://issues.apache.org/jira/browse/MESOS-1166 > Project: Mesos > Issue Type: Task >Reporter: Dave Lester >Assignee: Dave Lester > Labels: Conference, MesosCon > > An official announcement will follow, including attendee registration and > CFP. In the meantime, here are some additional details. Save the date! > August 21, 2014 > Chicago, IL > One day event, focused on Apache Mesos and its ecosystem. Morning will likely > include a workshop. > This event has been approved by the Mesos PMC and Apache Brand Management > committee. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (MESOS-649) Create Mesos blog planet?
[ https://issues.apache.org/jira/browse/MESOS-649?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester reassigned MESOS-649: - Assignee: Dave Lester > Create Mesos blog planet? > - > > Key: MESOS-649 > URL: https://issues.apache.org/jira/browse/MESOS-649 > Project: Mesos > Issue Type: Task >Reporter: Dave Lester >Assignee: Dave Lester >Priority: Minor > > Before I create an INFRA ticket to help set one up, what do folks think about > creating a blog planet for Mesos? I'm not sure many of us are currently > blogging, but it would be a good way to get the word out about the project > and encourage more community participation. > Additionally, any suggestions for who we would include? Any volunteers? -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1166) Planning MesosCon
[ https://issues.apache.org/jira/browse/MESOS-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester updated MESOS-1166: --- Description: An official announcement will follow, including attendee registration and CFP. In the meantime, here are some additional details. Save the date! August 21, 2014 Chicago, IL One day event, focused on Apache Mesos and its ecosystem. Morning will likely include a workshop. This event has been approved by the Mesos PMC and Apache Brand Management committee. was:Planning the first Apache Mesos conference: MesosCon. Target date is August 2014. > Planning MesosCon > - > > Key: MESOS-1166 > URL: https://issues.apache.org/jira/browse/MESOS-1166 > Project: Mesos > Issue Type: Task >Reporter: Dave Lester >Assignee: Dave Lester > Labels: Conference, MesosCon > > An official announcement will follow, including attendee registration and > CFP. In the meantime, here are some additional details. Save the date! > August 21, 2014 > Chicago, IL > One day event, focused on Apache Mesos and its ecosystem. Morning will likely > include a workshop. > This event has been approved by the Mesos PMC and Apache Brand Management > committee. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (MESOS-570) Generate Javadocs
[ https://issues.apache.org/jira/browse/MESOS-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13958347#comment-13958347 ] Dave Lester edited comment on MESOS-570 at 4/2/14 11:57 PM: Now online: http://mesos.apache.org/api/latest/java/, applying Tobi's patch with the minor change I suggested. was (Author: davelester): Now online: http://mesos.apache.org/api/current/java/, applying Tobi's patch with the minor change I suggested. > Generate Javadocs > - > > Key: MESOS-570 > URL: https://issues.apache.org/jira/browse/MESOS-570 > Project: Mesos > Issue Type: Sub-task >Reporter: Dave Lester >Assignee: Tobi Knaup > Attachments: javadoc.diff > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (MESOS-570) Generate Javadocs
[ https://issues.apache.org/jira/browse/MESOS-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester resolved MESOS-570. --- Resolution: Fixed Now online: http://mesos.apache.org/api/current/java/, applying Tobi's patch with the minor change I suggested. > Generate Javadocs > - > > Key: MESOS-570 > URL: https://issues.apache.org/jira/browse/MESOS-570 > Project: Mesos > Issue Type: Sub-task >Reporter: Dave Lester >Assignee: Tobi Knaup > Attachments: javadoc.diff > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-570) Generate Javadocs
[ https://issues.apache.org/jira/browse/MESOS-570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13958318#comment-13958318 ] Dave Lester commented on MESOS-570: --- I assume that changing the "current" directory name to "latest" is fine -- that will continue the url pattern used by our documentation urls (/documentation/latest/) > Generate Javadocs > - > > Key: MESOS-570 > URL: https://issues.apache.org/jira/browse/MESOS-570 > Project: Mesos > Issue Type: Sub-task >Reporter: Dave Lester >Assignee: Tobi Knaup > Attachments: javadoc.diff > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (MESOS-1166) Planning MesosCon
Dave Lester created MESOS-1166: -- Summary: Planning MesosCon Key: MESOS-1166 URL: https://issues.apache.org/jira/browse/MESOS-1166 Project: Mesos Issue Type: Task Reporter: Dave Lester Assignee: Dave Lester Planning the first Apache Mesos conference: MesosCon. Target date is August 2014. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (MESOS-1111) Add map to Mesos user group page
Dave Lester created MESOS-: -- Summary: Add map to Mesos user group page Key: MESOS- URL: https://issues.apache.org/jira/browse/MESOS- Project: Mesos Issue Type: Task Components: project website Reporter: Dave Lester This may not be as compelling with currently 2 user groups, but as we become more international with having Mesos User Groups we should add a map to our MUG page: http://mesos.apache.org/community/user-groups/ -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1110) Create Academic Papers and Project History Documentation
[ https://issues.apache.org/jira/browse/MESOS-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester updated MESOS-1110: --- Component/s: documentation > Create Academic Papers and Project History Documentation > > > Key: MESOS-1110 > URL: https://issues.apache.org/jira/browse/MESOS-1110 > Project: Mesos > Issue Type: Task > Components: documentation, project website >Reporter: Dave Lester > > We've had a stub for a "Academic Papers and Project History" page in the > documentation since we revamped it; we should make sure to add this either as > one page or two separate documentation pages. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (MESOS-1109) Improve the visual flow of the Getting Started page
Dave Lester created MESOS-1109: -- Summary: Improve the visual flow of the Getting Started page Key: MESOS-1109 URL: https://issues.apache.org/jira/browse/MESOS-1109 Project: Mesos Issue Type: Task Components: project website Reporter: Dave Lester Currently, the website's Getting Started page is large blocks of commends; we should figure out a way to make this page more easily-consumable, and appealing to look at. Maybe it's just a matter of modifying the page CSS, or doing more-radical changes to the content. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (MESOS-1110) Create Academic Papers and Project History Documentation
Dave Lester created MESOS-1110: -- Summary: Create Academic Papers and Project History Documentation Key: MESOS-1110 URL: https://issues.apache.org/jira/browse/MESOS-1110 Project: Mesos Issue Type: Task Components: project website Reporter: Dave Lester We've had a stub for a "Academic Papers and Project History" page in the documentation since we revamped it; we should make sure to add this either as one page or two separate documentation pages. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (MESOS-1108) Update homepage of website to include logos for adopters
Dave Lester created MESOS-1108: -- Summary: Update homepage of website to include logos for adopters Key: MESOS-1108 URL: https://issues.apache.org/jira/browse/MESOS-1108 Project: Mesos Issue Type: Task Components: project website Reporter: Dave Lester Increase the presence of adopters on the homepage, possibly featuring a montage of logos. This could be static, or optionally dynamic with side-scrolling. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (MESOS-1107) Create screencast for Getting Started with Mesos
Dave Lester created MESOS-1107: -- Summary: Create screencast for Getting Started with Mesos Key: MESOS-1107 URL: https://issues.apache.org/jira/browse/MESOS-1107 Project: Mesos Issue Type: Task Components: documentation Reporter: Dave Lester Priority: Minor It'd be great to have a video screencast that walks people through the steps of building Mesos and running example framework instructions that are included on the Getting Started page http://mesos.apache.org/gettingstarted/ -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (MESOS-1032) Apache Mesos logo is missing trademark
[ https://issues.apache.org/jira/browse/MESOS-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester updated MESOS-1032: --- Attachment: mesos_draft.png > Apache Mesos logo is missing trademark > --- > > Key: MESOS-1032 > URL: https://issues.apache.org/jira/browse/MESOS-1032 > Project: Mesos > Issue Type: Bug >Reporter: Jake Farrell >Assignee: Dave Lester > Attachments: mesos_draft.png > > > The Apache Mesos logo needs to have a tm added to it > http://www.apache.org/foundation/marks/pmcs.html#graphics -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (MESOS-1032) Apache Mesos logo is missing trademark
[ https://issues.apache.org/jira/browse/MESOS-1032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13932612#comment-13932612 ] Dave Lester commented on MESOS-1032: Below is the Aurora logo with the tm added; if it looks good I'll make sure this change is reflected on the website as well. !mesos_draft.png! > Apache Mesos logo is missing trademark > --- > > Key: MESOS-1032 > URL: https://issues.apache.org/jira/browse/MESOS-1032 > Project: Mesos > Issue Type: Bug >Reporter: Jake Farrell >Assignee: Dave Lester > Attachments: mesos_draft.png > > > The Apache Mesos logo needs to have a tm added to it > http://www.apache.org/foundation/marks/pmcs.html#graphics -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (MESOS-942) The link on "App/Framework development guide" is broken on the Mesos Code Internals page
[ https://issues.apache.org/jira/browse/MESOS-942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester resolved MESOS-942. --- Resolution: Fixed > The link on "App/Framework development guide" is broken on the Mesos Code > Internals page > - > > Key: MESOS-942 > URL: https://issues.apache.org/jira/browse/MESOS-942 > Project: Mesos > Issue Type: Bug > Components: documentation >Reporter: Bernardo Gomez Palacio >Assignee: Dave Lester >Priority: Minor > > In the Mesos Code Internal page < > http://mesos.apache.org/documentation/latest/mesos-code-internals/ > the link > "App/Framework development guide" is broken. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (MESOS-716) docs/Using-Linux-Containers.textile suggests removed lxc isolation
[ https://issues.apache.org/jira/browse/MESOS-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester closed MESOS-716. - Resolution: Not A Problem Closing this issue, because this file was previously removed. > docs/Using-Linux-Containers.textile suggests removed lxc isolation > -- > > Key: MESOS-716 > URL: https://issues.apache.org/jira/browse/MESOS-716 > Project: Mesos > Issue Type: Bug > Components: documentation >Reporter: Charles Reiss >Priority: Minor > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (MESOS-1011) Relative links are broken within documentation
[ https://issues.apache.org/jira/browse/MESOS-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester resolved MESOS-1011. Resolution: Fixed Fix proposed by [~tknaup] https://gist.github.com/guenter/9263548, which I've committed and it did the trick. Thanks, Tobi! > Relative links are broken within documentation > -- > > Key: MESOS-1011 > URL: https://issues.apache.org/jira/browse/MESOS-1011 > Project: Mesos > Issue Type: Bug > Components: documentation, project website >Reporter: Dave Lester >Assignee: Tobi Knaup > > We need relative links within documentation pages to be fixed. In particular, > this is broken for pages that are in subdirectories. > For example, on the Configuration page > http://mesos.apache.org/documentation/latest/configuration/, the link to High > Availability links to > http://mesos.apache.org/documentation/latest/configuration/high-availability > instead of http://mesos.apache.org/documentation/latest/high-availability -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (MESOS-1011) Relative links are broken within documentation
[ https://issues.apache.org/jira/browse/MESOS-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester reassigned MESOS-1011: -- Assignee: Tobi Knaup (was: Jake Farrell) > Relative links are broken within documentation > -- > > Key: MESOS-1011 > URL: https://issues.apache.org/jira/browse/MESOS-1011 > Project: Mesos > Issue Type: Bug > Components: documentation, project website >Reporter: Dave Lester >Assignee: Tobi Knaup > > We need relative links within documentation pages to be fixed. In particular, > this is broken for pages that are in subdirectories. > For example, on the Configuration page > http://mesos.apache.org/documentation/latest/configuration/, the link to High > Availability links to > http://mesos.apache.org/documentation/latest/configuration/high-availability > instead of http://mesos.apache.org/documentation/latest/high-availability -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (MESOS-1011) Relative links are broken within documentation
[ https://issues.apache.org/jira/browse/MESOS-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13915154#comment-13915154 ] Dave Lester commented on MESOS-1011: [~jfarrell] any further thoughts on a fix? This bug is particularly problematic since we've created the separate tools page that mostly includes relative links: http://mesos.apache.org/documentation/latest/tools/ cc [~ssorallen] > Relative links are broken within documentation > -- > > Key: MESOS-1011 > URL: https://issues.apache.org/jira/browse/MESOS-1011 > Project: Mesos > Issue Type: Bug > Components: documentation, project website >Reporter: Dave Lester >Assignee: Jake Farrell > > We need relative links within documentation pages to be fixed. In particular, > this is broken for pages that are in subdirectories. > For example, on the Configuration page > http://mesos.apache.org/documentation/latest/configuration/, the link to High > Availability links to > http://mesos.apache.org/documentation/latest/configuration/high-availability > instead of http://mesos.apache.org/documentation/latest/high-availability -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Reopened] (MESOS-1011) Relative links are broken within documentation
[ https://issues.apache.org/jira/browse/MESOS-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester reopened MESOS-1011: Reopening this; I was mistaken and the bug still exists. > Relative links are broken within documentation > -- > > Key: MESOS-1011 > URL: https://issues.apache.org/jira/browse/MESOS-1011 > Project: Mesos > Issue Type: Bug > Components: documentation, project website >Reporter: Dave Lester >Assignee: Jake Farrell > > We need relative links within documentation pages to be fixed. In particular, > this is broken for pages that are in subdirectories. > For example, on the Configuration page > http://mesos.apache.org/documentation/latest/configuration/, the link to High > Availability links to > http://mesos.apache.org/documentation/latest/configuration/high-availability > instead of http://mesos.apache.org/documentation/latest/high-availability -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (MESOS-1012) Alternatively strip md extensions from documentation pages
[ https://issues.apache.org/jira/browse/MESOS-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester resolved MESOS-1012. Resolution: Fixed Perfect, thanks [~jfarrell]! This is now committed. > Alternatively strip md extensions from documentation pages > -- > > Key: MESOS-1012 > URL: https://issues.apache.org/jira/browse/MESOS-1012 > Project: Mesos > Issue Type: Bug > Components: documentation, project website >Reporter: Dave Lester >Assignee: Jake Farrell > Attachments: MESOS-1012.patch, MESOS-1012_v2.patch > > > In the website Rakefile > http://svn.apache.org/viewvc/mesos/site/Rakefile?view=markup, we currently > strip .md from all links on documentation pages using sed. This was necessary > to remove the file extensions from urls. > However, this solution doesn't work for urls that begin with .md, for example > www.mdsol.com (a Mesos adopter) is having their url improperly altered when > it is built for the website. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (MESOS-1011) Relative links are broken within documentation
[ https://issues.apache.org/jira/browse/MESOS-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester resolved MESOS-1011. Resolution: Fixed Looks like [~jfarrell]'s patch for MESOS-1012 also fixed this. Thanks! > Relative links are broken within documentation > -- > > Key: MESOS-1011 > URL: https://issues.apache.org/jira/browse/MESOS-1011 > Project: Mesos > Issue Type: Bug > Components: documentation, project website >Reporter: Dave Lester >Assignee: Jake Farrell > > We need relative links within documentation pages to be fixed. In particular, > this is broken for pages that are in subdirectories. > For example, on the Configuration page > http://mesos.apache.org/documentation/latest/configuration/, the link to High > Availability links to > http://mesos.apache.org/documentation/latest/configuration/high-availability > instead of http://mesos.apache.org/documentation/latest/high-availability -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (MESOS-1012) Alternatively strip md extensions from documentation pages
[ https://issues.apache.org/jira/browse/MESOS-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13907541#comment-13907541 ] Dave Lester commented on MESOS-1012: Thanks for this; I ran into an issue though. The links everywhere else in the documentation are broken with this patch -- urls shouldn't have .md extensions when middleman renders them the upgrade url as a cool url, like http://mesos.apache.org/documentation/latest/upgrades/, not http://mesos.apache.org/documentation/latest/upgrades.md > Alternatively strip md extensions from documentation pages > -- > > Key: MESOS-1012 > URL: https://issues.apache.org/jira/browse/MESOS-1012 > Project: Mesos > Issue Type: Bug > Components: documentation, project website >Reporter: Dave Lester >Assignee: Jake Farrell > Attachments: MESOS-1012.patch > > > In the website Rakefile > http://svn.apache.org/viewvc/mesos/site/Rakefile?view=markup, we currently > strip .md from all links on documentation pages using sed. This was necessary > to remove the file extensions from urls. > However, this solution doesn't work for urls that begin with .md, for example > www.mdsol.com (a Mesos adopter) is having their url improperly altered when > it is built for the website. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (MESOS-1018) Implement Libprocess Benchmark Suite
Dave Lester created MESOS-1018: -- Summary: Implement Libprocess Benchmark Suite Key: MESOS-1018 URL: https://issues.apache.org/jira/browse/MESOS-1018 Project: Mesos Issue Type: Improvement Reporter: Dave Lester Implement a benchmark suite for libprocess to identify potential performance improvements and test for performance regressions. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (MESOS-1017) Mesos CLI improvements
[ https://issues.apache.org/jira/browse/MESOS-1017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester resolved MESOS-1017. Resolution: Duplicate > Mesos CLI improvements > -- > > Key: MESOS-1017 > URL: https://issues.apache.org/jira/browse/MESOS-1017 > Project: Mesos > Issue Type: Improvement > Components: cli >Reporter: Dave Lester > Labels: gsoc2014 > > Add new functionality to the Mesos CLI to make developers lives easier. > More-specific features should be added attached as sub-issues. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (MESOS-1017) Mesos CLI improvements
Dave Lester created MESOS-1017: -- Summary: Mesos CLI improvements Key: MESOS-1017 URL: https://issues.apache.org/jira/browse/MESOS-1017 Project: Mesos Issue Type: Improvement Components: cli Reporter: Dave Lester Add new functionality to the Mesos CLI to make developers lives easier. More-specific features should be added attached as sub-issues. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (MESOS-1016) Mesos CLI improvements
Dave Lester created MESOS-1016: -- Summary: Mesos CLI improvements Key: MESOS-1016 URL: https://issues.apache.org/jira/browse/MESOS-1016 Project: Mesos Issue Type: Improvement Components: cli Reporter: Dave Lester Add new functionality to the Mesos CLI to make developers lives easier. More-specific features should be added attached as sub-issues. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (MESOS-544) Mesos-slave support for "node drain"
[
https://issues.apache.org/jira/browse/MESOS-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Lester updated MESOS-544:
--
Labels: gsoc2014 (was: )
> Mesos-slave support for "node drain"
>
>
> Key: MESOS-544
> URL: https://issues.apache.org/jira/browse/MESOS-544
> Project: Mesos
> Issue Type: Story
> Components: documentation, framework, master, slave
>Reporter: Tobias Weingartner
> Labels: gsoc2014
> Fix For: 0.19.0
>
>
> Given that multiple frameworks can be present on a machine at a time, and
> writing "node drain" for each possible framework is an intractable task, it
> would nice if the slave-master core had a means to tell frameworks that tasks
> were killed to drain a host. Or possibly that the slave was told to drain
> the host of all tasks (graceful shutdown, etc).
> {noformat}
> # drain current host
> pkill -USR1 mesos-slave
> {noformat}
> This would make writing scripts for site-ops to do node maintenance much
> easier... :)
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
[jira] [Created] (MESOS-1012) Alternatively strip md extensions from documentation pages
Dave Lester created MESOS-1012: -- Summary: Alternatively strip md extensions from documentation pages Key: MESOS-1012 URL: https://issues.apache.org/jira/browse/MESOS-1012 Project: Mesos Issue Type: Bug Components: documentation, project website Reporter: Dave Lester Assignee: Jake Farrell In the website Rakefile http://svn.apache.org/viewvc/mesos/site/Rakefile?view=markup, we currently strip .md from all links on documentation pages using sed. This was necessary to remove the file extensions from urls. However, this solution doesn't work for urls that begin with .md, for example www.mdsol.com (a Mesos adopter) is having their url improperly altered when it is built for the website. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (MESOS-1011) Relative links are broken within documentation
[ https://issues.apache.org/jira/browse/MESOS-1011?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13904556#comment-13904556 ] Dave Lester commented on MESOS-1011: Could be fixed by making modifications to the website Rakefile? http://svn.apache.org/viewvc/mesos/site/Rakefile?view=markup Not sure what the ideal situation is, especially if we want to preserve offline readability (currently, links between docs are all relative and work if you were to browse the docs on your local machine). > Relative links are broken within documentation > -- > > Key: MESOS-1011 > URL: https://issues.apache.org/jira/browse/MESOS-1011 > Project: Mesos > Issue Type: Bug > Components: documentation, project website >Reporter: Dave Lester >Assignee: Jake Farrell > > We need relative links within documentation pages to be fixed. In particular, > this is broken for pages that are in subdirectories. > For example, on the Configuration page > http://mesos.apache.org/documentation/latest/configuration/, the link to High > Availability links to > http://mesos.apache.org/documentation/latest/configuration/high-availability > instead of http://mesos.apache.org/documentation/latest/high-availability -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (MESOS-1011) Relative links are broken within documentation
Dave Lester created MESOS-1011: -- Summary: Relative links are broken within documentation Key: MESOS-1011 URL: https://issues.apache.org/jira/browse/MESOS-1011 Project: Mesos Issue Type: Bug Components: documentation, project website Reporter: Dave Lester Assignee: Jake Farrell We need relative links within documentation pages to be fixed. In particular, this is broken for pages that are in subdirectories. For example, on the Configuration page http://mesos.apache.org/documentation/latest/configuration/, the link to High Availability links to http://mesos.apache.org/documentation/latest/configuration/high-availability instead of http://mesos.apache.org/documentation/latest/high-availability -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (MESOS-562) Update 'Getting Started' Documentation Page
[ https://issues.apache.org/jira/browse/MESOS-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester resolved MESOS-562. --- Resolution: Fixed Fixed! Thanks for your patience, ya'll. > Update 'Getting Started' Documentation Page > --- > > Key: MESOS-562 > URL: https://issues.apache.org/jira/browse/MESOS-562 > Project: Mesos > Issue Type: Sub-task >Reporter: Dave Lester >Assignee: Dave Lester > Labels: twitter > Fix For: 0.19.0 > > -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Closed] (MESOS-829) Switch website CMS from Jekyll to Middleman
[ https://issues.apache.org/jira/browse/MESOS-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester closed MESOS-829. - Resolution: Fixed Fixed. Thanks for your help, [~jfarrell]! > Switch website CMS from Jekyll to Middleman > --- > > Key: MESOS-829 > URL: https://issues.apache.org/jira/browse/MESOS-829 > Project: Mesos > Issue Type: Improvement > Components: project website >Reporter: Dave Lester >Assignee: Jake Farrell >Priority: Critical > Attachments: site.tar.gz > > > We currently use Jekyll as the CMS to manage the Mesos website. It does most > of what we need by offering templates and power to control how pages render. > The only issue is that when you build from source files Jekyll will wipe away > any hidden files in the rendered directory. This is problematic since both > the source and live directories are in version control (svn). Our recent > website revision history has been a mess, because we often end up wiping > out/rewriting > I'd like to switch the site to use Middleman to render our static site files. > We are using Middleman for Apache Aurora, and it doesn't face the issue of > wiping out hidden files. Additionally, it seems capable of all the same > rendering features of Markdown that we currently use. The only difference is > that redcarpet (the library for converting markdown to HTML) needs to use > ruby 3+. > Thoughts? -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (MESOS-942) The link on "App/Framework development guide" is broken on the Mesos Code Internals page
[ https://issues.apache.org/jira/browse/MESOS-942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester reassigned MESOS-942: - Assignee: Dave Lester > The link on "App/Framework development guide" is broken on the Mesos Code > Internals page > - > > Key: MESOS-942 > URL: https://issues.apache.org/jira/browse/MESOS-942 > Project: Mesos > Issue Type: Bug > Components: documentation >Reporter: Bernardo Gomez Palacio >Assignee: Dave Lester >Priority: Minor > > In the Mesos Code Internal page < > http://mesos.apache.org/documentation/latest/mesos-code-internals/ > the link > "App/Framework development guide" is broken. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (MESOS-942) The link on "App/Framework development guide" is broken on the Mesos Code Internals page
[ https://issues.apache.org/jira/browse/MESOS-942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13880213#comment-13880213 ] Dave Lester commented on MESOS-942: --- Thanks for pointing this out, links within internal pages broke when the build script was previously modified; it's fixed with the new website and should go online soon as soon as INFRA-7216 (and subsequently, MESOS-829) is finished. > The link on "App/Framework development guide" is broken on the Mesos Code > Internals page > - > > Key: MESOS-942 > URL: https://issues.apache.org/jira/browse/MESOS-942 > Project: Mesos > Issue Type: Bug > Components: documentation >Reporter: Bernardo Gomez Palacio >Priority: Minor > > In the Mesos Code Internal page < > http://mesos.apache.org/documentation/latest/mesos-code-internals/ > the link > "App/Framework development guide" is broken. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (MESOS-829) Switch website CMS from Jekyll to Middleman
[ https://issues.apache.org/jira/browse/MESOS-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876963#comment-13876963 ] Dave Lester commented on MESOS-829: --- Great, I added to the Rakefile to remove the md extensions from documentation links, and pushed this change to subversion. Thanks [~jfarrell] for your huge help here. I've create a ticket, INFRA-7216, to switch SvnPubSub. After that's completed, I can clean up the remaining files in subversion. > Switch website CMS from Jekyll to Middleman > --- > > Key: MESOS-829 > URL: https://issues.apache.org/jira/browse/MESOS-829 > Project: Mesos > Issue Type: Improvement > Components: project website >Reporter: Dave Lester >Assignee: Jake Farrell >Priority: Critical > Attachments: site.tar.gz > > > We currently use Jekyll as the CMS to manage the Mesos website. It does most > of what we need by offering templates and power to control how pages render. > The only issue is that when you build from source files Jekyll will wipe away > any hidden files in the rendered directory. This is problematic since both > the source and live directories are in version control (svn). Our recent > website revision history has been a mess, because we often end up wiping > out/rewriting > I'd like to switch the site to use Middleman to render our static site files. > We are using Middleman for Apache Aurora, and it doesn't face the issue of > wiping out hidden files. Additionally, it seems capable of all the same > rendering features of Markdown that we currently use. The only difference is > that redcarpet (the library for converting markdown to HTML) needs to use > ruby 3+. > Thoughts? -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (MESOS-72) Finish moving open relevant issues from github issue tracker to Apache JIRA
[ https://issues.apache.org/jira/browse/MESOS-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester resolved MESOS-72. -- Resolution: Won't Fix Doing a little housekeeping, I went ahead and hid the old GitHub issue tracker. Since all of the remaining tickets were between 2-4 years old without activity and we've had 9 subsequent Mesos release, I think it's safe to assume that none are relevant any longer. Feel free to reopen this issue if you disagree. > Finish moving open relevant issues from github issue tracker to Apache JIRA > --- > > Key: MESOS-72 > URL: https://issues.apache.org/jira/browse/MESOS-72 > Project: Mesos > Issue Type: Task >Reporter: Andy Konwinski >Assignee: Adam Monsen >Priority: Minor > > There are still a number of issues that were reported while we were using the > github issue tracker (see https://github.com/mesos/mesos/issues) that need to > be moved to Apache JIRA -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Resolved] (MESOS-528) Mesos website refresh
[ https://issues.apache.org/jira/browse/MESOS-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester resolved MESOS-528. --- Resolution: Implemented Resolving this issue, since the website refresh happened many months ago. One suggested detail that was not included on the current site is a FAQ; I've created a new JIRA issue to track its development: MESOS-915 > Mesos website refresh > - > > Key: MESOS-528 > URL: https://issues.apache.org/jira/browse/MESOS-528 > Project: Mesos > Issue Type: Improvement >Reporter: Dave Lester >Assignee: Dave Lester > Labels: twitter > > - * Add required links to Mesos website: > https://issues.apache.org/jira/browse/MESOS-66- > - * Update the website to use new Mesos logo.- > - * Some visual changes to update the overall design of the site, which is a > bit dated...- > - * Making it easier for people to get started with Mesos by simplifying and > updating the site navigation to include 'getting started' and 'getting > involved.' Probably moving research and FAQ to the documentation.- > * Making it easy to find out who uses Mesos and why by adding a list of > active users to the homepage with logos. Testimonials could also be a way for > people understand who is using the project and why. > * Revamping of documentation (see > https://issues.apache.org/jira/browse/MESOS-511), a few issues are there and > I think there is a lot of work that can be done there. > -* Migrate website to a template system of some kind. > https://issues.apache.org/jira/browse/MESOS-495- -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (MESOS-915) Draft FAQ to be included in project documentation
Dave Lester created MESOS-915: - Summary: Draft FAQ to be included in project documentation Key: MESOS-915 URL: https://issues.apache.org/jira/browse/MESOS-915 Project: Mesos Issue Type: Documentation Components: documentation Reporter: Dave Lester Priority: Minor As suggested on the Mesos user mailing list, we're overdue for a FAQ on the Mesos website. I suggest including this in the project documentation (stored in the /docs/ folder) Could folks help suggest questions (and answers) to include? Just leave it in the comments for this issue. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (MESOS-865) Website build script should update relative links in docs before rendering
[ https://issues.apache.org/jira/browse/MESOS-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13869871#comment-13869871 ] Dave Lester commented on MESOS-865: --- bq. Can the .md extension be kept on the website URLs? No, the best-practice would be to leave off file-extensions. [Cool URIs don't change](http://www.w3.org/Provider/Style/URI.html) bq. Can the links be relative on the website, as opposed to absolute? I'm not sure, there were issues in the past but that may have just been a problem with the implementation. > Website build script should update relative links in docs before rendering > -- > > Key: MESOS-865 > URL: https://issues.apache.org/jira/browse/MESOS-865 > Project: Mesos > Issue Type: Bug > Components: project website >Affects Versions: 0.14.2 >Reporter: Till Toenshoff >Priority: Trivial > Labels: documentation, website > > On http://mesos.apache.org/documentation/latest/mesos-developers-guide/ at > the bottom, the link for "Mesos C++ Style Guide" > Points towards: > http://mesos.apache.org/documentation/latest/mesos-developers-guide/mesos-c++-style-guide > Should be pointing towards (I guess): > http://mesos.apache.org/documentation/latest/mesos-c++-style-guide -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (MESOS-865) Website build script should update relative links in docs before rendering
[ https://issues.apache.org/jira/browse/MESOS-865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868909#comment-13868909 ] Dave Lester commented on MESOS-865: --- I looked into this and updated the ticket accordingly. Within the docs folder, links to other documentation files are local links (ie: another-file.md) so users who are browsing them locally can navigate accordingly. We render these same files on the Mesos website by running a build script that strips .md from the paths to these local links. What it needs to additionally do is create the full link to the documentation pages. Does anyone have alternative solutions to modifying the build script? It may be worth waiting until MESOS-829 is live until someone works on this, since that ticket tentatively moves us from a shell script to using a Rake file. > Website build script should update relative links in docs before rendering > -- > > Key: MESOS-865 > URL: https://issues.apache.org/jira/browse/MESOS-865 > Project: Mesos > Issue Type: Bug > Components: project website >Affects Versions: 0.14.2 >Reporter: Till Toenshoff >Priority: Trivial > Labels: documentation, website > > On http://mesos.apache.org/documentation/latest/mesos-developers-guide/ at > the bottom, the link for "Mesos C++ Style Guide" > Points towards: > http://mesos.apache.org/documentation/latest/mesos-developers-guide/mesos-c++-style-guide > Should be pointing towards (I guess): > http://mesos.apache.org/documentation/latest/mesos-c++-style-guide -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (MESOS-865) Website build script should update relative links in docs before rendering
[ https://issues.apache.org/jira/browse/MESOS-865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester updated MESOS-865: -- Summary: Website build script should update relative links in docs before rendering (was: "Mesos C++ Style Guide" link on mesos-developers-guide broken) > Website build script should update relative links in docs before rendering > -- > > Key: MESOS-865 > URL: https://issues.apache.org/jira/browse/MESOS-865 > Project: Mesos > Issue Type: Bug > Components: project website >Affects Versions: 0.14.2 >Reporter: Till Toenshoff >Priority: Trivial > Labels: documentation, website > > On http://mesos.apache.org/documentation/latest/mesos-developers-guide/ at > the bottom, the link for "Mesos C++ Style Guide" > Points towards: > http://mesos.apache.org/documentation/latest/mesos-developers-guide/mesos-c++-style-guide > Should be pointing towards (I guess): > http://mesos.apache.org/documentation/latest/mesos-c++-style-guide -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (MESOS-418) Add security and authentication support to Mesos (including integration with LDAP).
[ https://issues.apache.org/jira/browse/MESOS-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13868161#comment-13868161 ] Dave Lester commented on MESOS-418: --- [~adam-mesos] Sounds great! As Vinod said, it would be great to create JIRA for each of these tasks. [~davidww95] Ping, in case you're still interested in contributing to this. > Add security and authentication support to Mesos (including integration with > LDAP). > --- > > Key: MESOS-418 > URL: https://issues.apache.org/jira/browse/MESOS-418 > Project: Mesos > Issue Type: Story >Reporter: Vinod Kone >Assignee: Ilim Ugur > Labels: c++, cloud, gsoc, gsoc2013, mentor > > The basic idea behind the proposal, is to add authorization/authentication > support to Mesos. For example, Mesos should only allow authenticated > frameworks to register and submit jobs. The plan is to leverage Kerberos/LDAP > to add this support. We are also open to suggestions on how we can add > support for security and auth in Mesos. > Knowledge Prerequisite: C++ -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (MESOS-897) Removal of HAVE_LIBZ and HAVE_CURL from .hpp files
[ https://issues.apache.org/jira/browse/MESOS-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866901#comment-13866901 ] Dave Lester commented on MESOS-897: --- Hi [~tstclair], could you please submit this to review board? > Removal of HAVE_LIBZ and HAVE_CURL from .hpp files > -- > > Key: MESOS-897 > URL: https://issues.apache.org/jira/browse/MESOS-897 > Project: Mesos > Issue Type: Bug > Components: build >Reporter: Timothy St. Clair >Assignee: Timothy St. Clair >Priority: Minor > Labels: patch > Attachments: MESOS-897.patch > > > Typically HAVE_XYZ are constraints that are checked from a dropped config.h > file. Given that both curl and zlib are hard constraints it makes sense to > remove them from stout. Attached patch contains mods to remove + some other > minor header cleaning. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (MESOS-829) Switch website CMS from Jekyll to Middleman
[ https://issues.apache.org/jira/browse/MESOS-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester updated MESOS-829: -- Attachment: (was: aurorawebsite_lester_010714.zip) > Switch website CMS from Jekyll to Middleman > --- > > Key: MESOS-829 > URL: https://issues.apache.org/jira/browse/MESOS-829 > Project: Mesos > Issue Type: Improvement > Components: project website >Reporter: Dave Lester >Assignee: Jake Farrell >Priority: Critical > Attachments: site.tar.gz > > > We currently use Jekyll as the CMS to manage the Mesos website. It does most > of what we need by offering templates and power to control how pages render. > The only issue is that when you build from source files Jekyll will wipe away > any hidden files in the rendered directory. This is problematic since both > the source and live directories are in version control (svn). Our recent > website revision history has been a mess, because we often end up wiping > out/rewriting > I'd like to switch the site to use Middleman to render our static site files. > We are using Middleman for Apache Aurora, and it doesn't face the issue of > wiping out hidden files. Additionally, it seems capable of all the same > rendering features of Markdown that we currently use. The only difference is > that redcarpet (the library for converting markdown to HTML) needs to use > ruby 3+. > Thoughts? -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (MESOS-829) Switch website CMS from Jekyll to Middleman
[ https://issues.apache.org/jira/browse/MESOS-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester updated MESOS-829: -- Attachment: aurorawebsite_lester_010714.zip > Switch website CMS from Jekyll to Middleman > --- > > Key: MESOS-829 > URL: https://issues.apache.org/jira/browse/MESOS-829 > Project: Mesos > Issue Type: Improvement > Components: project website >Reporter: Dave Lester >Assignee: Jake Farrell >Priority: Critical > Attachments: aurorawebsite_lester_010714.zip, site.tar.gz > > > We currently use Jekyll as the CMS to manage the Mesos website. It does most > of what we need by offering templates and power to control how pages render. > The only issue is that when you build from source files Jekyll will wipe away > any hidden files in the rendered directory. This is problematic since both > the source and live directories are in version control (svn). Our recent > website revision history has been a mess, because we often end up wiping > out/rewriting > I'd like to switch the site to use Middleman to render our static site files. > We are using Middleman for Apache Aurora, and it doesn't face the issue of > wiping out hidden files. Additionally, it seems capable of all the same > rendering features of Markdown that we currently use. The only difference is > that redcarpet (the library for converting markdown to HTML) needs to use > ruby 3+. > Thoughts? -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (MESOS-829) Switch website CMS from Jekyll to Middleman
[ https://issues.apache.org/jira/browse/MESOS-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13852108#comment-13852108 ] Dave Lester commented on MESOS-829: --- [~ssorallen] Yeah, I think i18n support is one of the huge selling points of Middleman. [~jfarrell] Awesome, thanks for your help! > Switch website CMS from Jekyll to Middleman > --- > > Key: MESOS-829 > URL: https://issues.apache.org/jira/browse/MESOS-829 > Project: Mesos > Issue Type: Improvement > Components: project website >Reporter: Dave Lester >Assignee: Dave Lester >Priority: Critical > > We currently use Jekyll as the CMS to manage the Mesos website. It does most > of what we need by offering templates and power to control how pages render. > The only issue is that when you build from source files Jekyll will wipe away > any hidden files in the rendered directory. This is problematic since both > the source and live directories are in version control (svn). Our recent > website revision history has been a mess, because we often end up wiping > out/rewriting > I'd like to switch the site to use Middleman to render our static site files. > We are using Middleman for Apache Aurora, and it doesn't face the issue of > wiping out hidden files. Additionally, it seems capable of all the same > rendering features of Markdown that we currently use. The only difference is > that redcarpet (the library for converting markdown to HTML) needs to use > ruby 3+. > Thoughts? -- This message was sent by Atlassian JIRA (v6.1.4#6159)
[jira] [Commented] (MESOS-829) Switch website CMS from Jekyll to Middleman
[ https://issues.apache.org/jira/browse/MESOS-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13831108#comment-13831108 ] Dave Lester commented on MESOS-829: --- [~everpeace] looks like localization is possible with Middleman. http://middlemanapp.com/advanced/localization/ > Switch website CMS from Jekyll to Middleman > --- > > Key: MESOS-829 > URL: https://issues.apache.org/jira/browse/MESOS-829 > Project: Mesos > Issue Type: Improvement > Components: project website >Reporter: Dave Lester >Assignee: Dave Lester >Priority: Critical > > We currently use Jekyll as the CMS to manage the Mesos website. It does most > of what we need by offering templates and power to control how pages render. > The only issue is that when you build from source files Jekyll will wipe away > any hidden files in the rendered directory. This is problematic since both > the source and live directories are in version control (svn). Our recent > website revision history has been a mess, because we often end up wiping > out/rewriting > I'd like to switch the site to use Middleman to render our static site files. > We are using Middleman for Apache Aurora, and it doesn't face the issue of > wiping out hidden files. Additionally, it seems capable of all the same > rendering features of Markdown that we currently use. The only difference is > that redcarpet (the library for converting markdown to HTML) needs to use > ruby 3+. > Thoughts? -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (MESOS-829) Switch website CMS from Jekyll to Middleman
Dave Lester created MESOS-829: - Summary: Switch website CMS from Jekyll to Middleman Key: MESOS-829 URL: https://issues.apache.org/jira/browse/MESOS-829 Project: Mesos Issue Type: Improvement Components: project website Reporter: Dave Lester Assignee: Dave Lester Priority: Critical We currently use Jekyll as the CMS to manage the Mesos website. It does most of what we need by offering templates and power to control how pages render. The only issue is that when you build from source files Jekyll will wipe away any hidden files in the rendered directory. This is problematic since both the source and live directories are in version control (svn). Our recent website revision history has been a mess, because we often end up wiping out/rewriting I'd like to switch the site to use Middleman to render our static site files. We are using Middleman for Apache Aurora, and it doesn't face the issue of wiping out hidden files. Additionally, it seems capable of all the same rendering features of Markdown that we currently use. The only difference is that redcarpet (the library for converting markdown to HTML) needs to use ruby 3+. Thoughts? -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (MESOS-780) Adding support for 3rd party performance and health monitoring.
[ https://issues.apache.org/jira/browse/MESOS-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13814190#comment-13814190 ] Dave Lester commented on MESOS-780: --- [~berngp] Are you currently working on this? Would be interesting to gather requirements. Maybe you could ping the user and dev lists to see if anyone else has other tools they'd like to integrate with. > Adding support for 3rd party performance and health monitoring. > --- > > Key: MESOS-780 > URL: https://issues.apache.org/jira/browse/MESOS-780 > Project: Mesos > Issue Type: Improvement > Components: framework >Reporter: Bernardo Gomez Palacio > > User Story: > As a SysAdmin I should be able to monitor Mesos (Masters and Slaves) with > 3rd party tools such as: > * [Ganglia|http://ganglia.sourceforge.net/] > * [Graphite|http://graphite.wikidot.com/] > * [Nagios|http://www.nagios.org/] > * [Zabbix|http://www.zabbix.com/] -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (MESOS-556) November 2013 Documentation Overhaul
[ https://issues.apache.org/jira/browse/MESOS-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester updated MESOS-556: -- Summary: November 2013 Documentation Overhaul (was: July 2013 Documentation Overhaul) > November 2013 Documentation Overhaul > > > Key: MESOS-556 > URL: https://issues.apache.org/jira/browse/MESOS-556 > Project: Mesos > Issue Type: Documentation >Reporter: Dave Lester >Assignee: Dave Lester >Priority: Critical > > The Mesos documentation is due for an overhaul -- we haven't consistently > updated the docs for new releases, and it would be great to review its > current state in light of our soon-to-by-launched website refresh. > I'll go ahead and create sub-tasks for each of the pages we will keep -- help > out by claiming sub-tasks! -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Closed] (MESOS-575) Update or delete 'Mesos Ready to go AMI' Documentation Page
[ https://issues.apache.org/jira/browse/MESOS-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester closed MESOS-575. - Resolution: Implemented Since it was out of date and no longer maintained, the Mesos API page was deleted in the recent documentation changes: https://reviews.apache.org/r/14923/. I'll mark this as implemented. > Update or delete 'Mesos Ready to go AMI' Documentation Page > --- > > Key: MESOS-575 > URL: https://issues.apache.org/jira/browse/MESOS-575 > Project: Mesos > Issue Type: Sub-task >Reporter: Dave Lester > > It's my understanding that the AMI is no longer being maintained. Is that > correct, [~woggle]? In that case, should I delete it? -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (MESOS-511) Update documentation home and remove outdated drafts pages
[ https://issues.apache.org/jira/browse/MESOS-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester resolved MESOS-511. --- Resolution: Implemented These changes were implemented in this review: https://reviews.apache.org/r/14923/ > Update documentation home and remove outdated drafts pages > -- > > Key: MESOS-511 > URL: https://issues.apache.org/jira/browse/MESOS-511 > Project: Mesos > Issue Type: Documentation >Reporter: Dave Lester >Assignee: Dave Lester >Priority: Minor > > Update the documentation home for increased readability. Create a separate > getting started page in the docs, and also remove unused and outdated draft > documentation. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (MESOS-744) Possibly move /docs/ folder out of Mesos core, into separate repo
[ https://issues.apache.org/jira/browse/MESOS-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester resolved MESOS-744. --- Resolution: Won't Fix For rendering markdown on the website, I've found a solution requires far fewer changes and will allow us to keep the docs folder within the main Mesos repository. My other motivation of making it easy for folks to edit documentation is still alive, but I think it's best to approach that issue comprehensively including documentation AND the core (particularly if they are in a shared repo). Therefore, I'm going to close this issue for now. Feel free to reopen if you disagree, or if at some point in the future we decide that moving /docs/ into a separate repository makes sense. > Possibly move /docs/ folder out of Mesos core, into separate repo > - > > Key: MESOS-744 > URL: https://issues.apache.org/jira/browse/MESOS-744 > Project: Mesos > Issue Type: Documentation >Reporter: Dave Lester >Assignee: Dave Lester >Priority: Minor > > I'd like to propose moving the /docs/ folder out of the Mesos core, and into > a separate repo on github. This is a good idea for a few reasons, including: > 1) We could easily share the repo between Mesos git repository (/docs/ would > included as a submodule), as well imported into the Mesos website. Currently, > docs files are not used in the Mesos website, so we have to send users to > github to view rendered markdown. Breaking it into a separate repo would > would make it simple for us to render the docs at mesos.apache.org > 2) It would be significantly easier for community members to contribute. A > simple pull request could make minor changes. In fact, a number of these > changes have already been made to the documentation > (https://github.com/apache/mesos/pulls), but we have no current way to > process them. Right now our process requires the same level of complexity and > creating unique Apache accounts if they want to make simple updates to the > documentation. > 3) It could provide an opportunity for community ownership of the docs, which > at this point have tended to be an afterthought of core developers. > The only main disadvantage that I see in this approach would be maintaining > an additional repository and possible coordination in releases, however I see > this as relatively minor. The specifics of how this affects tagging could be > discussed further, I don't feel strongly about it. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (MESOS-748) Add blog to Mesos website
[ https://issues.apache.org/jira/browse/MESOS-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802940#comment-13802940 ] Dave Lester commented on MESOS-748: --- The basic blog is now online: http://mesos.apache.org/blog/ Includes an initial blog post by Vinod about the Slave Recovery feature in Mesos http://mesos.apache.org/blog/slave-recovery-in-apache-mesos/ > Add blog to Mesos website > - > > Key: MESOS-748 > URL: https://issues.apache.org/jira/browse/MESOS-748 > Project: Mesos > Issue Type: Improvement >Reporter: Dave Lester >Assignee: Dave Lester >Priority: Critical > > I'd like an official blog on the Mesos website to announce releases, and > feature posts from committers about various features that are being worked on > or have appeared in recent releases. For example, I spoke to Vinod Kone about > a possible post on slave recovery that we could feature. It'd also be nice to > include more description than the brief announcements we currently make on > the homepage. It's simple to set this up using Jekyll. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (MESOS-748) Add blog to Mesos website
[ https://issues.apache.org/jira/browse/MESOS-748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester resolved MESOS-748. --- Resolution: Fixed > Add blog to Mesos website > - > > Key: MESOS-748 > URL: https://issues.apache.org/jira/browse/MESOS-748 > Project: Mesos > Issue Type: Improvement >Reporter: Dave Lester >Assignee: Dave Lester >Priority: Critical > > I'd like an official blog on the Mesos website to announce releases, and > feature posts from committers about various features that are being worked on > or have appeared in recent releases. For example, I spoke to Vinod Kone about > a possible post on slave recovery that we could feature. It'd also be nice to > include more description than the brief announcements we currently make on > the homepage. It's simple to set this up using Jekyll. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (MESOS-748) Add blog to Mesos website
[ https://issues.apache.org/jira/browse/MESOS-748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13799406#comment-13799406 ] Dave Lester commented on MESOS-748: --- Some concerns: * It looks like blogs.apache.org doesn't have many adopters, despite being around for a while. It's unclear to me what Mesos gains by starting a blog there vs mesos.apache.org. * The web design of blogs.apache.org looks out-of-date and clunky. Additional points: * If we host the blog at mesos.apache.org, we can still have posts aggregated at planet.apache.org. I think this would similarly facilitate the discovery of posts within the Apache community. * Hosting at mesos.apache.org would help our SEO, adding new keywords to find our website. I'd like to see blog posts increase our overall web traffic. > Add blog to Mesos website > - > > Key: MESOS-748 > URL: https://issues.apache.org/jira/browse/MESOS-748 > Project: Mesos > Issue Type: Improvement >Reporter: Dave Lester >Assignee: Dave Lester >Priority: Critical > > I'd like an official blog on the Mesos website to announce releases, and > feature posts from committers about various features that are being worked on > or have appeared in recent releases. For example, I spoke to Vinod Kone about > a possible post on slave recovery that we could feature. It'd also be nice to > include more description than the brief announcements we currently make on > the homepage. It's simple to set this up using Jekyll. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (MESOS-748) Add blog to Mesos website
Dave Lester created MESOS-748: - Summary: Add blog to Mesos website Key: MESOS-748 URL: https://issues.apache.org/jira/browse/MESOS-748 Project: Mesos Issue Type: Improvement Reporter: Dave Lester Assignee: Dave Lester Priority: Critical I'd like an official blog on the Mesos website to announce releases, and feature posts from committers about various features that are being worked on or have appeared in recent releases. For example, I spoke to Vinod Kone about a possible post on slave recovery that we could feature. It'd also be nice to include more description than the brief announcements we currently make on the homepage. It's simple to set this up using Jekyll. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (MESOS-744) Possibly move /docs/ folder out of Mesos core, into separate repo
[ https://issues.apache.org/jira/browse/MESOS-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796466#comment-13796466 ] Dave Lester commented on MESOS-744: --- Currently, the Mesos website uses Jekyll to render a set of template files. Right now, we link externally to github (such as https://github.com/apache/mesos/blob/master/docs/Configuration.md) because they render markdown files for us. There's no way to easily import and render those same files if they're just a folder within the main mesos repository. If the docs were their own repository that's separate from both the Mesos core and the website, we could easily automate the process of rendering them within mesos.apache.org by including and rendering them on the mesos website. Make sense? Your idea about automating the creation of RB requests is interesting, perhaps [~chrismattmann] or [~jfarrell] know of other projects who are handling GH pull requests that way. For the purposes of this issue, though, I'm focused on docs -- if we'd like to investage using github pull requests for the core I think that should be a separate issue. > Possibly move /docs/ folder out of Mesos core, into separate repo > - > > Key: MESOS-744 > URL: https://issues.apache.org/jira/browse/MESOS-744 > Project: Mesos > Issue Type: Documentation >Reporter: Dave Lester >Assignee: Dave Lester >Priority: Minor > > I'd like to propose moving the /docs/ folder out of the Mesos core, and into > a separate repo on github. This is a good idea for a few reasons, including: > 1) We could easily share the repo between Mesos git repository (/docs/ would > included as a submodule), as well imported into the Mesos website. Currently, > docs files are not used in the Mesos website, so we have to send users to > github to view rendered markdown. Breaking it into a separate repo would > would make it simple for us to render the docs at mesos.apache.org > 2) It would be significantly easier for community members to contribute. A > simple pull request could make minor changes. In fact, a number of these > changes have already been made to the documentation > (https://github.com/apache/mesos/pulls), but we have no current way to > process them. Right now our process requires the same level of complexity and > creating unique Apache accounts if they want to make simple updates to the > documentation. > 3) It could provide an opportunity for community ownership of the docs, which > at this point have tended to be an afterthought of core developers. > The only main disadvantage that I see in this approach would be maintaining > an additional repository and possible coordination in releases, however I see > this as relatively minor. The specifics of how this affects tagging could be > discussed further, I don't feel strongly about it. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Comment Edited] (MESOS-744) Possibly move /docs/ folder out of Mesos core, into separate repo
[ https://issues.apache.org/jira/browse/MESOS-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796459#comment-13796459 ] Dave Lester edited comment on MESOS-744 at 10/16/13 5:59 AM: - It may be a little tricky to respond to each point but assume each of my bullet points corresponds to yours: --> Can you elaborate on your issues with git submodules? I've used them in other projects without any issues. --> It will become confusing if we take github pull requests for certain content in github.com/apache/mesos/ (such as the /docs/ folder), but not the rest of the repo. AFAIK Apache only mirrors the repository -- they don't allow us to actually administer the repositories or sync backwards so I'm not sure how you'd suggest us accepting pull requests through the regular github.com/apache/mesos/ repo. What's unique about documentation is that we don't require someone to sign a CLA if they edit the docs or wiki -- separating it would make that clear to users. --> I don't think it's necessarily more difficult, I just think we need to figure out a process for doing so. I don't see that as a blocker in any way. The motivation of this switch is to cleanly share docs between the distribution of Mesos and the website; using git submodules can help. I don't see a way to do that with the current setup or alternatives, but I'm open to suggestions. was (Author: davelester): It may be a little tricky to respond to each point but assume each of my bullet points corresponds to yours: --> Can you elaborate on your issues with git submodules? I've used them in other projects without any issues. --> It will become confusing if we take github pull requests for certain content in github.com/apache/mesos/ (such as the /docs/ folder), but not the rest of the repo. Additionally, AFAIK Apache only mirrors the repository -- they don't allow us to actually administer the repositories or sync backwards so I'm not sure how you'd suggest us accepting pull requests through the regular github.com/apache/mesos/ repo. What's unique about documentation is that we don't require someone to sign a CLA if they edit the docs or wiki -- separating it would make that clear to users. --> I don't think it's necessarily more difficult, I just think we need to figure out a process for doing so. I don't see that as a blocker in any way. The motivation of this switch is to cleanly share docs between the distribution of Mesos and the website; using git submodules can help. I don't see a way to do that with the current setup or alternatives, but I'm open to suggestions. > Possibly move /docs/ folder out of Mesos core, into separate repo > - > > Key: MESOS-744 > URL: https://issues.apache.org/jira/browse/MESOS-744 > Project: Mesos > Issue Type: Documentation >Reporter: Dave Lester >Assignee: Dave Lester >Priority: Minor > > I'd like to propose moving the /docs/ folder out of the Mesos core, and into > a separate repo on github. This is a good idea for a few reasons, including: > 1) We could easily share the repo between Mesos git repository (/docs/ would > included as a submodule), as well imported into the Mesos website. Currently, > docs files are not used in the Mesos website, so we have to send users to > github to view rendered markdown. Breaking it into a separate repo would > would make it simple for us to render the docs at mesos.apache.org > 2) It would be significantly easier for community members to contribute. A > simple pull request could make minor changes. In fact, a number of these > changes have already been made to the documentation > (https://github.com/apache/mesos/pulls), but we have no current way to > process them. Right now our process requires the same level of complexity and > creating unique Apache accounts if they want to make simple updates to the > documentation. > 3) It could provide an opportunity for community ownership of the docs, which > at this point have tended to be an afterthought of core developers. > The only main disadvantage that I see in this approach would be maintaining > an additional repository and possible coordination in releases, however I see > this as relatively minor. The specifics of how this affects tagging could be > discussed further, I don't feel strongly about it. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Comment Edited] (MESOS-744) Possibly move /docs/ folder out of Mesos core, into separate repo
[ https://issues.apache.org/jira/browse/MESOS-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796459#comment-13796459 ] Dave Lester edited comment on MESOS-744 at 10/16/13 5:59 AM: - It may be a little tricky to respond to each point but assume each of my bullet points corresponds to yours: --> Can you elaborate on your issues with git submodules? I've used them in other projects without any issues. --> It will become confusing if we take github pull requests for certain content in github.com/apache/mesos/ (such as the /docs/ folder), but not the rest of the repo. Additionally, AFAIK Apache only mirrors the repository -- they don't allow us to actually administer the repositories or sync backwards so I'm not sure how you'd suggest us accepting pull requests through the regular github.com/apache/mesos/ repo. What's unique about documentation is that we don't require someone to sign a CLA if they edit the docs or wiki -- separating it would make that clear to users. --> I don't think it's necessarily more difficult, I just think we need to figure out a process for doing so. I don't see that as a blocker in any way. The motivation of this switch is to cleanly share docs between the distribution of Mesos and the website; using git submodules can help. I don't see a way to do that with the current setup or alternatives, but I'm open to suggestions. was (Author: davelester): It may be a little tricky to respond to each point but assume each of my bullet points corresponds to yours: --> Can you elaborate on your issues with git submodules? I've used them in other projects without any issues. --> It will become confusing if we take github pull requests for certain content in github.com/apache/mesos/ (such as the /docs/ folder), but not the rest of the repo. Additionally, AFAIK Apache only mirrors the repository -- they don't allow us to actually administer the repositories or sync backwards so I'm not sure how you'd suggest us accepting pull requests through the regular github.com/apache/mesos/ repo. What's unique about documentation is that we don't require someone to sign a CLA if they edit the docs or wiki -- separating it would make that clear to users. --> I don't think it's necessarily more difficult, I just think we need to figure out a process for doing so. I don't see that as a blocker in any way. Additionally, the motivation of this switch is to cleanly share docs between the distribution of Mesos and the website; using git submodules can help. I don't see a way to do that with the current setup or alternatives, but I'm open to suggestions. > Possibly move /docs/ folder out of Mesos core, into separate repo > - > > Key: MESOS-744 > URL: https://issues.apache.org/jira/browse/MESOS-744 > Project: Mesos > Issue Type: Documentation >Reporter: Dave Lester >Assignee: Dave Lester >Priority: Minor > > I'd like to propose moving the /docs/ folder out of the Mesos core, and into > a separate repo on github. This is a good idea for a few reasons, including: > 1) We could easily share the repo between Mesos git repository (/docs/ would > included as a submodule), as well imported into the Mesos website. Currently, > docs files are not used in the Mesos website, so we have to send users to > github to view rendered markdown. Breaking it into a separate repo would > would make it simple for us to render the docs at mesos.apache.org > 2) It would be significantly easier for community members to contribute. A > simple pull request could make minor changes. In fact, a number of these > changes have already been made to the documentation > (https://github.com/apache/mesos/pulls), but we have no current way to > process them. Right now our process requires the same level of complexity and > creating unique Apache accounts if they want to make simple updates to the > documentation. > 3) It could provide an opportunity for community ownership of the docs, which > at this point have tended to be an afterthought of core developers. > The only main disadvantage that I see in this approach would be maintaining > an additional repository and possible coordination in releases, however I see > this as relatively minor. The specifics of how this affects tagging could be > discussed further, I don't feel strongly about it. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (MESOS-744) Possibly move /docs/ folder out of Mesos core, into separate repo
[ https://issues.apache.org/jira/browse/MESOS-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13796459#comment-13796459 ] Dave Lester commented on MESOS-744: --- It may be a little tricky to respond to each point but assume each of my bullet points corresponds to yours: --> Can you elaborate on your issues with git submodules? I've used them in other projects without any issues. --> It will become confusing if we take github pull requests for certain content in github.com/apache/mesos/ (such as the /docs/ folder), but not the rest of the repo. Additionally, AFAIK Apache only mirrors the repository -- they don't allow us to actually administer the repositories or sync backwards so I'm not sure how you'd suggest us accepting pull requests through the regular github.com/apache/mesos/ repo. What's unique about documentation is that we don't require someone to sign a CLA if they edit the docs or wiki -- separating it would make that clear to users. --> I don't think it's necessarily more difficult, I just think we need to figure out a process for doing so. I don't see that as a blocker in any way. Additionally, the motivation of this switch is to cleanly share docs between the distribution of Mesos and the website; using git submodules can help. I don't see a way to do that with the current setup or alternatives, but I'm open to suggestions. > Possibly move /docs/ folder out of Mesos core, into separate repo > - > > Key: MESOS-744 > URL: https://issues.apache.org/jira/browse/MESOS-744 > Project: Mesos > Issue Type: Documentation >Reporter: Dave Lester >Assignee: Dave Lester >Priority: Minor > > I'd like to propose moving the /docs/ folder out of the Mesos core, and into > a separate repo on github. This is a good idea for a few reasons, including: > 1) We could easily share the repo between Mesos git repository (/docs/ would > included as a submodule), as well imported into the Mesos website. Currently, > docs files are not used in the Mesos website, so we have to send users to > github to view rendered markdown. Breaking it into a separate repo would > would make it simple for us to render the docs at mesos.apache.org > 2) It would be significantly easier for community members to contribute. A > simple pull request could make minor changes. In fact, a number of these > changes have already been made to the documentation > (https://github.com/apache/mesos/pulls), but we have no current way to > process them. Right now our process requires the same level of complexity and > creating unique Apache accounts if they want to make simple updates to the > documentation. > 3) It could provide an opportunity for community ownership of the docs, which > at this point have tended to be an afterthought of core developers. > The only main disadvantage that I see in this approach would be maintaining > an additional repository and possible coordination in releases, however I see > this as relatively minor. The specifics of how this affects tagging could be > discussed further, I don't feel strongly about it. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Created] (MESOS-744) Possibly move /docs/ folder out of Mesos core, into separate repo
Dave Lester created MESOS-744: - Summary: Possibly move /docs/ folder out of Mesos core, into separate repo Key: MESOS-744 URL: https://issues.apache.org/jira/browse/MESOS-744 Project: Mesos Issue Type: Documentation Reporter: Dave Lester Assignee: Dave Lester Priority: Minor I'd like to propose moving the /docs/ folder out of the Mesos core, and into a separate repo on github. This is a good idea for a few reasons, including: 1) We could easily share the repo between Mesos git repository (/docs/ would included as a submodule), as well imported into the Mesos website. Currently, docs files are not used in the Mesos website, so we have to send users to github to view rendered markdown. Breaking it into a separate repo would would make it simple for us to render the docs at mesos.apache.org 2) It would be significantly easier for community members to contribute. A simple pull request could make minor changes. In fact, a number of these changes have already been made to the documentation (https://github.com/apache/mesos/pulls), but we have no current way to process them. Right now our process requires the same level of complexity and creating unique Apache accounts if they want to make simple updates to the documentation. 3) It could provide an opportunity for community ownership of the docs, which at this point have tended to be an afterthought of core developers. The only main disadvantage that I see in this approach would be maintaining an additional repository and possible coordination in releases, however I see this as relatively minor. The specifics of how this affects tagging could be discussed further, I don't feel strongly about it. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Resolved] (MESOS-66) Add required links to Mesos website
[ https://issues.apache.org/jira/browse/MESOS-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester resolved MESOS-66. -- Resolution: Fixed Good call, [~ssorallen]. This ticket was fixed when the new website launched. > Add required links to Mesos website > --- > > Key: MESOS-66 > URL: https://issues.apache.org/jira/browse/MESOS-66 > Project: Mesos > Issue Type: Task > Components: project-website >Reporter: Andy Konwinski >Assignee: Dave Lester >Priority: Minor > > Add the required links listed at > http://www.apache.org/foundation/marks/pmcs.html#navigation to the Mesos > website. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (MESOS-518) Improve README with Markdown
[ https://issues.apache.org/jira/browse/MESOS-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13769830#comment-13769830 ] Dave Lester commented on MESOS-518: --- Patch submitted: https://reviews.apache.org/r/14172/ > Improve README with Markdown > > > Key: MESOS-518 > URL: https://issues.apache.org/jira/browse/MESOS-518 > Project: Mesos > Issue Type: Documentation > Components: documentation >Reporter: Chris Aniszczyk >Assignee: Dave Lester >Priority: Minor > Fix For: 0.15.0 > > > If you go to the github mirror of Mesos, the README doesn't look nice: > https://github.com/apache/incubator-mesos/blob/master/README > We should move to Markdown format so GitHub renders it nicely: > https://help.github.com/articles/github-flavored-markdown -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MESOS-697) Make it clear how to update website vs documentation vs core
Dave Lester created MESOS-697: - Summary: Make it clear how to update website vs documentation vs core Key: MESOS-697 URL: https://issues.apache.org/jira/browse/MESOS-697 Project: Mesos Issue Type: Documentation Reporter: Dave Lester Assignee: Dave Lester Currently, the Developer Guide doesn't make it clear how we manage our website, vs the documentation and the Mesos core. We should make this crystal clear so more folks can contribute. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MESOS-665) Update "Using Zookeeper" link from website to point to the "High Availability" document instead.
[ https://issues.apache.org/jira/browse/MESOS-665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester resolved MESOS-665. --- Resolution: Fixed Committed revision 1522091. > Update "Using Zookeeper" link from website to point to the "High > Availability" document instead. > > > Key: MESOS-665 > URL: https://issues.apache.org/jira/browse/MESOS-665 > Project: Mesos > Issue Type: Task > Components: documentation >Reporter: Benjamin Mahler >Assignee: Dave Lester > > This was reported here: > https://github.com/apache/mesos/pull/2 > This page has a broken link: > http://mesos.apache.org/documentation/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MESOS-618) Remove Hadoop on Mesos from repository in favor of external repository
[ https://issues.apache.org/jira/browse/MESOS-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester resolved MESOS-618. --- Resolution: Fixed > Remove Hadoop on Mesos from repository in favor of external repository > -- > > Key: MESOS-618 > URL: https://issues.apache.org/jira/browse/MESOS-618 > Project: Mesos > Issue Type: Task >Affects Versions: 0.9.0, 0.10.0, 0.11.0, 0.12.0, 0.12.1 >Reporter: Benjamin Hindman >Assignee: Benjamin Hindman > Fix For: 0.13.0 > > > Hadoop on Mesos is currently done as a "contrib" of a Hadoop distribution. We > "make this work" via a very complicated "tutorial" which builds a Hadoop on > Mesos distribution. This is unnecessary. Work has been made by others to > simplify running Hadoop on Mesos (see github.com/mesos/hadoop). Using Mesos > as the repository for Hadoop on Mesos doesn't make sense because it doesn't > allow it to easily operate independently of what's happing in Mesos itself. > Moreover, the contributors to Hadoop on Mesos could be very different to the > contributors to Apache Mesos itself. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MESOS-618) Remove Hadoop on Mesos from repository in favor of external repository
[ https://issues.apache.org/jira/browse/MESOS-618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13764459#comment-13764459 ] Dave Lester commented on MESOS-618: --- These changes were made, and Hadoop was moved to a separate repository: http://github.com/mesos/hadoop > Remove Hadoop on Mesos from repository in favor of external repository > -- > > Key: MESOS-618 > URL: https://issues.apache.org/jira/browse/MESOS-618 > Project: Mesos > Issue Type: Task >Affects Versions: 0.9.0, 0.10.0, 0.11.0, 0.12.0, 0.12.1 >Reporter: Benjamin Hindman >Assignee: Benjamin Hindman > Fix For: 0.13.0 > > > Hadoop on Mesos is currently done as a "contrib" of a Hadoop distribution. We > "make this work" via a very complicated "tutorial" which builds a Hadoop on > Mesos distribution. This is unnecessary. Work has been made by others to > simplify running Hadoop on Mesos (see github.com/mesos/hadoop). Using Mesos > as the repository for Hadoop on Mesos doesn't make sense because it doesn't > allow it to easily operate independently of what's happing in Mesos itself. > Moreover, the contributors to Hadoop on Mesos could be very different to the > contributors to Apache Mesos itself. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MESOS-345) The downloads page for Mesos contains a link to the VM which is confusing since it's not an official Apache product
[ https://issues.apache.org/jira/browse/MESOS-345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester resolved MESOS-345. --- Resolution: Fixed Good call, this was ditched when the new site when live. > The downloads page for Mesos contains a link to the VM which is confusing > since it's not an official Apache product > --- > > Key: MESOS-345 > URL: https://issues.apache.org/jira/browse/MESOS-345 > Project: Mesos > Issue Type: Task > Components: documentation > Environment: http://incubator.apache.org/mesos/download.html >Reporter: Chris A. Mattmann >Assignee: Dave Lester >Priority: Blocker > > The Apache Mesos (incubating) download page has a link to a pre-packaged VM > not built at Apache, but built downstream in the AMPLab at Berkeley. This is > fine, but should be spelled out explicitly on the page a lot clearer than it > is now. It's confusing right now b/c it seems like the VM is an Apache > product even though it redirects to an external site. > To pass muster with trademarks@ we need to make sure this is updated before > graduation. Thanks! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MESOS-649) Create Mesos blog planet?
Dave Lester created MESOS-649: - Summary: Create Mesos blog planet? Key: MESOS-649 URL: https://issues.apache.org/jira/browse/MESOS-649 Project: Mesos Issue Type: Task Reporter: Dave Lester Priority: Minor Before I create an INFRA ticket to help set one up, what do folks think about creating a blog planet for Mesos? I'm not sure many of us are currently blogging, but it would be a good way to get the word out about the project and encourage more community participation. Additionally, any suggestions for who we would include? Any volunteers? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MESOS-622) Mesos website does not load properly over HTTPS
[ https://issues.apache.org/jira/browse/MESOS-622?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester resolved MESOS-622. --- Resolution: Fixed > Mesos website does not load properly over HTTPS > --- > > Key: MESOS-622 > URL: https://issues.apache.org/jira/browse/MESOS-622 > Project: Mesos > Issue Type: Bug >Reporter: Dave Lester > > As pointed out by several people including [~ssorallen], > https://mesos.apache.org/ references its assets over HTTP, which some > browsers block because it's considered a different domain. > The origin of the problem is that the Jekyll templates which build the site > have http hardcoded in the url, located in _config.yml in the subversion > repo: https://svn.apache.org/repos/asf/mesos/website > We need the urls of css/js includes, as well as images be relative -- and > also work for urls like mesos.apache.org/documentation/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MESOS-622) Mesos website does not load properly over HTTPS
[ https://issues.apache.org/jira/browse/MESOS-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735488#comment-13735488 ] Dave Lester commented on MESOS-622: --- Thanks, this did the trick! > Mesos website does not load properly over HTTPS > --- > > Key: MESOS-622 > URL: https://issues.apache.org/jira/browse/MESOS-622 > Project: Mesos > Issue Type: Bug >Reporter: Dave Lester > > As pointed out by several people including [~ssorallen], > https://mesos.apache.org/ references its assets over HTTP, which some > browsers block because it's considered a different domain. > The origin of the problem is that the Jekyll templates which build the site > have http hardcoded in the url, located in _config.yml in the subversion > repo: https://svn.apache.org/repos/asf/mesos/website > We need the urls of css/js includes, as well as images be relative -- and > also work for urls like mesos.apache.org/documentation/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (MESOS-495) Migrate to a template system for the website
[ https://issues.apache.org/jira/browse/MESOS-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Lester resolved MESOS-495. --- Resolution: Fixed > Migrate to a template system for the website > > > Key: MESOS-495 > URL: https://issues.apache.org/jira/browse/MESOS-495 > Project: Mesos > Issue Type: Task > Components: project-website >Reporter: Andy Konwinski >Assignee: Dave Lester > > It's somewhat painful to update the news items, nav system, footers, etc. on > each page of the website. We should embrace DRY and use some system to make > this easy. > I've used and like Jekyll (http://jekyllrb.com/) which uses liquid templates > (http://wiki.shopify.com/Liquid) and can work over top of markup or, as I > propose in our case, straight HTML. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MESOS-495) Migrate to a template system for the website
[ https://issues.apache.org/jira/browse/MESOS-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735476#comment-13735476 ] Dave Lester commented on MESOS-495: --- Jekyll templates are being stored in the website/ directory on subversion, and the live Mesos website that is built from these templates exists in www/. I've also added a README file with instructions in version control: https://svn.apache.org/repos/asf/mesos/ > Migrate to a template system for the website > > > Key: MESOS-495 > URL: https://issues.apache.org/jira/browse/MESOS-495 > Project: Mesos > Issue Type: Task > Components: project-website >Reporter: Andy Konwinski >Assignee: Dave Lester > > It's somewhat painful to update the news items, nav system, footers, etc. on > each page of the website. We should embrace DRY and use some system to make > this easy. > I've used and like Jekyll (http://jekyllrb.com/) which uses liquid templates > (http://wiki.shopify.com/Liquid) and can work over top of markup or, as I > propose in our case, straight HTML. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MESOS-562) Update 'Getting Started' Documentation Page
[ https://issues.apache.org/jira/browse/MESOS-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735459#comment-13735459 ] Dave Lester commented on MESOS-562: --- Any updates on this? > Update 'Getting Started' Documentation Page > --- > > Key: MESOS-562 > URL: https://issues.apache.org/jira/browse/MESOS-562 > Project: Mesos > Issue Type: Sub-task >Reporter: Dave Lester >Assignee: Vinod Kone > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (MESOS-622) Mesos website does not load properly over HTTPS
[ https://issues.apache.org/jira/browse/MESOS-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13731469#comment-13731469 ] Dave Lester commented on MESOS-622: --- Can someone help out here? I looked through relevant jekyllrb.com documentation, but couldn't find the best-practice for dealing with this. > Mesos website does not load properly over HTTPS > --- > > Key: MESOS-622 > URL: https://issues.apache.org/jira/browse/MESOS-622 > Project: Mesos > Issue Type: Bug >Reporter: Dave Lester > > As pointed out by several people including [~ssorallen], > https://mesos.apache.org/ references its assets over HTTP, which some > browsers block because it's considered a different domain. > The origin of the problem is that the Jekyll templates which build the site > have http hardcoded in the url, located in _config.yml in the subversion > repo: https://svn.apache.org/repos/asf/mesos/website > We need the urls of css/js includes, as well as images be relative -- and > also work for urls like mesos.apache.org/documentation/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (MESOS-622) Mesos website does not load properly over HTTPS
Dave Lester created MESOS-622: - Summary: Mesos website does not load properly over HTTPS Key: MESOS-622 URL: https://issues.apache.org/jira/browse/MESOS-622 Project: Mesos Issue Type: Bug Reporter: Dave Lester As pointed out by several people including [~ssorallen], https://mesos.apache.org/ references its assets over HTTP, which some browsers block because it's considered a different domain. The origin of the problem is that the Jekyll templates which build the site have http hardcoded in the url, located in _config.yml in the subversion repo: https://svn.apache.org/repos/asf/mesos/website We need the urls of css/js includes, as well as images be relative -- and also work for urls like mesos.apache.org/documentation/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
