RE: help needed
Hi Subhasis, You might want to checkout https://incubator.apache.org/guides/proposal.html Regards Srikanth Sundarrajan - From: subhasis.go...@gmail.com Date: Sat, 22 Mar 2014 09:42:44 +0530 Subject: help needed To: general@incubator.apache.org Hello, I had a query - basically sometime back I had submitted one project idea to this forum. I'm totally new to this process. I had gone through the docs but didn't quite get the it very clearly. I'm yet to receive any feedback or suggestion from you. I'm not sure, the idea could be very simple or flimsy - but still I would look for your valuable suggestions. That would help me a lot in future. I'm sharing the outline of my idea again - https://drive.google.com/file/d/0B9Q1BwMfX5KcOWZaZk5TZmxodjg/edit?usp=sharing Github Repo: https://github.com/subhasisgorai/HQuery/tree/master/MyMSWork I thank you in anticipation .. - Subhasis Gorai - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache ODF Toolkit 0.6.1-incubating
On Wed, Feb 19, 2014 at 9:07 AM, Rob Weir robw...@apache.org wrote: We've had a vote within the PPMC which passed: http://mail-archives.apache.org/mod_mbox/incubator-odf-dev/201402.mbox/%3CCAP-ksogUFy-OkDkdJcNYDjnn8wUf%3DxcJX%2BG2xxQLKzp5PGKEgA%40mail.gmail.com%3E We're now looking for review and approval by the IPMC. Regards, -Rob -- RC4 for the ODF Toolkit 0.6.1-incubating release is available at: http://people.apache.org/~robweir/odftoolkit-release/odftoolkit-0.6.1-incubating/ The release candidate is a zip archive of the sources in: https://svn.apache.org/repos/asf/incubator/odf/tags/odftoolkit-0.6.1-incubating-RC4/ We're voting on the odftoolkit-0.6.1-incubating-src.zip. Please vote on releasing this package as Apache ODF Toolkit 0.6.1-incubating. If the vote passes we'll also distribute pre-built binaries and JavaDoc as a convenience to users, as well as publish to Maven. The vote is open for the next 72 hours and passes if a majority of at least three +1 PMC votes are cast. [ ] +1 Release this package as Apache ODF Toolkit 0.6.1-incubating [ ] -1 Do not release this package because... I'll upgrade my vote to +1 (binding) That gives us two +1's from the IPMC. Need one more to release. I realize many are busy (including me) finishing up ApacheCon slides. But if someone else can take a look I'd appreciate it greatly. Regards, -Rob - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Flagging up retired podlings on the website
At present, often the only indication that podling is retired is that podlings.xml has been updated. Some podlings may include a note on their status page (Alois), others (Awf) don't. Neither Alois nor Awf have any indication on their web-pages that the podling has been retired. As well as updating the News section of the status pages, I think it would be worth considering adding an obvious banner to the start of the status page: And perhaps add a banner to the web pages, similar to what is done for Atiic projects, for example: http://harmony.apache.org/ - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: help needed
On Sun, Mar 23, 2014 at 9:54 PM, Subhasis Gorai subhasis.go...@gmail.com wrote: Basically, I felt, before coming up with the proposal I need to get a champion who will guide me. Now I didn't know how to find a champion and that's the reason I had shared the idea, anticipating if someone is interested helping me out. The Incubator and the ASF are primarily here to support communities which have formed around software projects. For the most part, we don't gate on technical concerns -- an idea could be really great but it has to get a community in order to become part of the ASF. Proposing an idea directly on general@incubator is not necessarily the most effective way to start a community around an idea because the subscribers here would only be in the target audience for a software product by chance. Or to look at things from another angle, the response on general@incubator to a technical proposal is not a good measure of its potential, since we are more set up to assess the potential of communities. So if this cold start on general@incubator doesn't yield the desired result, perhaps consider other means of drawing contributors to your project -- blog posts, conference speaking, helpful mailing-list contributions on related projects, etc. Then, if that initiative is successful, perhaps return to the Incubator with your new collaborators. HTH, Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Rearrange the Project List into multiple pages?
On Sat, Mar 22, 2014 at 9:17 AM, sebb seb...@gmail.com wrote: The Project List [1] currently shows full details for all podlings past and present in a single rather long page. It might be better to have individual pages for the current/graduated/retired podlings, with a much simpler one-line summary of all the podlings on the existing page. I like the idea of paring down the information on the Project List page regardless. As for breaking things up into three pages... it may not be necessary once the rows shrink. The summary could contain just the name, resourcename, status and enddate (if relevant) For example Agila agila retired 2006-12-05 Airavata airavata graduated 2012-09-19 Allura alluracurrent I'd suggest Project, Status and Dates. The resourcename is only of interest to a limited audience and it can be derived from the URL for the podling status webpage, right? My suggestion would be to omit it. * The Project field should link to the project website: TLP site for graduated podlings, podling website for podlings currently in incubation, unlinked for retired podlings. * The Status field should link to the podling's incubation status page. (e.g. http://incubator.apache.org/projects/foo.html) * The Dates field should include both start date and end date, separated by an en dash (`ndash;`) flanked by spaces: `2012-01-01 - 2013-12-31`. For podlings still in incubation, the end date could be replaced with present: `2014-01-01 - present` Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Flagging up retired podlings on the website
On Mon, Mar 24, 2014 at 8:17 AM, sebb seb...@gmail.com wrote: At present, often the only indication that podling is retired is that podlings.xml has been updated. Some podlings may include a note on their status page (Alois), others (Awf) don't. Neither Alois nor Awf have any indication on their web-pages that the podling has been retired. As well as updating the News section of the status pages, I think it would be worth considering adding an obvious banner to the start of the status page: And perhaps add a banner to the web pages, similar to what is done for Atiic projects, for example: http://harmony.apache.org/ This was discussed back in 2011. http://markmail.org/message/7t7iv66wgv5nug5m Consensus coalesced around Christian Grobmeier's suggestion that we introduce a redirect to the podling status page. Apparently we still need to do the work of puttting in the redirects for a number of retired podlings. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Flagging up retired podlings on the website
On 24 March 2014 21:09, Marvin Humphrey mar...@rectangular.com wrote: On Mon, Mar 24, 2014 at 8:17 AM, sebb seb...@gmail.com wrote: At present, often the only indication that podling is retired is that podlings.xml has been updated. Some podlings may include a note on their status page (Alois), others (Awf) don't. Neither Alois nor Awf have any indication on their web-pages that the podling has been retired. As well as updating the News section of the status pages, I think it would be worth considering adding an obvious banner to the start of the status page: And perhaps add a banner to the web pages, similar to what is done for Atiic projects, for example: http://harmony.apache.org/ This was discussed back in 2011. http://markmail.org/message/7t7iv66wgv5nug5m Consensus coalesced around Christian Grobmeier's suggestion that we introduce a redirect to the podling status page. Apparently we still need to do the work of puttting in the redirects for a number of retired podlings. That's much easier to do than updating the website. I'll add the missing redirects. And once that has been done, the contents won't be accessible externally so such websites can presumably then be deleted? Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Flagging up retired podlings on the website
On Mon, Mar 24, 2014 at 5:20 PM, sebb seb...@gmail.com wrote: That's much easier to do than updating the website. I'll add the missing redirects. Excellent, thank you sebb! And once that has been done, the contents won't be accessible externally so such websites can presumably then be deleted? +1 Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Rearrange the Project List into multiple pages?
On 24 March 2014 20:56, Marvin Humphrey mar...@rectangular.com wrote: On Sat, Mar 22, 2014 at 9:17 AM, sebb seb...@gmail.com wrote: The Project List [1] currently shows full details for all podlings past and present in a single rather long page. It might be better to have individual pages for the current/graduated/retired podlings, with a much simpler one-line summary of all the podlings on the existing page. I like the idea of paring down the information on the Project List page regardless. As for breaking things up into three pages... it may not be necessary once the rows shrink. The summary could contain just the name, resourcename, status and enddate (if relevant) For example Agila agila retired 2006-12-05 Airavata airavata graduated 2012-09-19 Allura alluracurrent I'd suggest Project, Status and Dates. The resourcename is only of interest to a limited audience and it can be derived from the URL for the podling status webpage, right? Not always, for example OpenOffice.org = ooo The usecase for the resourcename (perhaps resourceAlias) is to access SVN My suggestion would be to omit it. * The Project field should link to the project website: TLP site for graduated podlings, podling website for podlings currently in incubation, unlinked for retired podlings. * The Status field should link to the podling's incubation status page. (e.g. http://incubator.apache.org/projects/foo.html) * The Dates field should include both start date and end date, separated by an en dash (`ndash;`) flanked by spaces: `2012-01-01 - 2013-12-31`. For podlings still in incubation, the end date could be replaced with present: `2014-01-01 - present` Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Rearrange the Project List into multiple pages?
On Tue, 25 Mar 2014, at 12:06 PM, sebb wrote: On 24 March 2014 20:56, Marvin Humphrey mar...@rectangular.com wrote: On Sat, Mar 22, 2014 at 9:17 AM, sebb seb...@gmail.com wrote: The Project List [1] currently shows full details for all podlings past and present in a single rather long page. It might be better to have individual pages for the current/graduated/retired podlings, with a much simpler one-line summary of all the podlings on the existing page. I like the idea of paring down the information on the Project List page regardless. As for breaking things up into three pages... it may not be necessary once the rows shrink. The summary could contain just the name, resourcename, status and enddate (if relevant) For example Agila agila retired 2006-12-05 Airavata airavata graduated 2012-09-19 Allura alluracurrent I'd suggest Project, Status and Dates. The resourcename is only of interest to a limited audience and it can be derived from the URL for the podling status webpage, right? Not always, for example OpenOffice.org = ooo The usecase for the resourcename (perhaps resourceAlias) is to access SVN Also for poor Clutch to try to keep up with the inconsistency of project names. -David My suggestion would be to omit it. * The Project field should link to the project website: TLP site for graduated podlings, podling website for podlings currently in incubation, unlinked for retired podlings. * The Status field should link to the podling's incubation status page. (e.g. http://incubator.apache.org/projects/foo.html) * The Dates field should include both start date and end date, separated by an en dash (`ndash;`) flanked by spaces: `2012-01-01 - 2013-12-31`. For podlings still in incubation, the end date could be replaced with present: `2014-01-01 - present` Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Rearrange the Project List into multiple pages?
On 25 March 2014 01:18, David Crossley cross...@apache.org wrote: On Tue, 25 Mar 2014, at 12:06 PM, sebb wrote: On 24 March 2014 20:56, Marvin Humphrey mar...@rectangular.com wrote: On Sat, Mar 22, 2014 at 9:17 AM, sebb seb...@gmail.com wrote: The Project List [1] currently shows full details for all podlings past and present in a single rather long page. It might be better to have individual pages for the current/graduated/retired podlings, with a much simpler one-line summary of all the podlings on the existing page. I like the idea of paring down the information on the Project List page regardless. As for breaking things up into three pages... it may not be necessary once the rows shrink. The idea was not to lose all the existing data, most of which I think is only displayed on that page currently. The idea was to provide a summary in addition to the individual more detailed sections. The summary could contain just the name, resourcename, status and enddate (if relevant) For example Agila agila retired 2006-12-05 Airavata airavata graduated 2012-09-19 Allura alluracurrent I'd suggest Project, Status and Dates. The resourcename is only of interest to a limited audience and it can be derived from the URL for the podling status webpage, right? Not always, for example OpenOffice.org = ooo The usecase for the resourcename (perhaps resourceAlias) is to access SVN Also for poor Clutch to try to keep up with the inconsistency of project names. Yes, but Clutch uses podlings.xml directly. The question was whether the generated page should contain resourcename. It may also need to contain resourceAliases. -David My suggestion would be to omit it. * The Project field should link to the project website: TLP site for graduated podlings, podling website for podlings currently in incubation, unlinked for retired podlings. * The Status field should link to the podling's incubation status page. (e.g. http://incubator.apache.org/projects/foo.html) * The Dates field should include both start date and end date, separated by an en dash (`ndash;`) flanked by spaces: `2012-01-01 - 2013-12-31`. For podlings still in incubation, the end date could be replaced with present: `2014-01-01 - present` Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Rearrange the Project List into multiple pages?
sebb: Not always, for example OpenOffice.org = ooo The usecase for the resourcename (perhaps resourceAlias) is to access SVN Repositories are linked from the podling status page, though it is admittedly not as convenient to get there in two hops. Many recent podlings use Git -- often multiple repositories -- so linking to SVN is of limited use. If you really really want this I'm not going to object but I think it should be acknowledged that it's often inappropriate. David Crossley: Also for poor Clutch to try to keep up with the inconsistency of project names. Definitely the resource name is important for that purpose -- I'm simply questioning how much benefit we get from dedicating a field to it on the podling listing page. sebb once again: As for breaking things up into three pages... it may not be necessary once the rows shrink. The idea was not to lose all the existing data, most of which I think is only displayed on that page currently. Everything on that page is also duplicated on the podling status pages. If certain values are not in sync, I think we should acknowledge that and fix our DRY problems rather than add more duplication. The idea was to provide a summary in addition to the individual more detailed sections. Hmm. To be honest, I don't think that's justified. I think it's too many resources providing slightly different views of the same information. Another option would be to add JavaScript show/hide to the podling index page, where clicking on a podling reveals expanded data. I'm not in favor of that (too much work) but I mention it as another alternative to creating new web pages. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Rearrange the Project List into multiple pages?
On 25 March 2014 01:46, Marvin Humphrey mar...@rectangular.com wrote: sebb: Not always, for example OpenOffice.org = ooo The usecase for the resourcename (perhaps resourceAlias) is to access SVN Repositories are linked from the podling status page, though it is admittedly not as convenient to get there in two hops. Many recent podlings use Git -- often multiple repositories -- so linking to SVN is of limited use. If you really really want this I'm not going to object but I think it should be acknowledged that it's often inappropriate. David Crossley: Also for poor Clutch to try to keep up with the inconsistency of project names. Definitely the resource name is important for that purpose -- I'm simply questioning how much benefit we get from dedicating a field to it on the podling listing page. sebb once again: As for breaking things up into three pages... it may not be necessary once the rows shrink. The idea was not to lose all the existing data, most of which I think is only displayed on that page currently. Everything on that page is also duplicated on the podling status pages. I think that's not the case. If certain values are not in sync, I think we should acknowledge that and fix our DRY problems rather than add more duplication. podlings.xml was introduced because the status pages don't include the data in a usable fashion for automated processing. It's also useful to have the basic information in a single file which can be subject to DTDs etc. The status files are free-form xml/xhtml Maybe it would be possible to automate the inclusion of the relevant bits from podlings.xml into the individual status files. But that seems like a lot of work for not much reward. The idea was to provide a summary in addition to the individual more detailed sections. Hmm. To be honest, I don't think that's justified. I think it's too many resources providing slightly different views of the same information. The problem is that the current page has useful information but has become unwieldy. Rather than just split it 3, I think a summary would be useful. There's no full alphabetical listing of all podling names currently so this provides a useful additional resource. Another option would be to add JavaScript show/hide to the podling index page, where clicking on a podling reveals expanded data. I'm not in favor of that (too much work) but I mention it as another alternative to creating new web pages. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
