moving on, plus Incubator facilities documentation and tools
It is time for me to move on from the Apache Incubator. I feel that i have done as much as is possible. There is various documentation to try to assist people and projects to help themselves: http://incubator.apache.org/facilities.html http://wiki.apache.org/incubator/IncubatorIssues2013 If any of my past stuff needs clarification, then contact me directly. -David - 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 01:14 PM, sebb wrote: 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 Also the podlings.xml was introduced because projects do not keep their status pages up-to-date. Being more concise it should be easier to manage, and tools can verify it and utilise it. 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 last time that we went through this, there was a suggestion to trim the status page template to just provide links to the various bits of summary information that are generated from podlings.xml file. -David 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
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: Marking retired podlings in SVN
On Tue, 18 Mar 2014, at 07:09 AM, sebb wrote: Just wondering whether it might be useful to add a RETIRED marker file to the top-level SVN directory of podlings that have retired? Good idea. Add that as another step to: http://incubator.apache.org/guides/retirement.html Ideally it would be the last thing done to SVN. In that way the last log message seen via 'viewvc' web interface also makes it clear. It could just be an empty file, or it could contain a link to the retired summary status, for example: http://incubator.apache.org/projects/index.html#agila The link would be good. I'm happy to make a start on that if it's thought useful. Yes, i think so. -David - 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 Thu, Mar 6, 2014, at 06:43 AM, sebb wrote: On 5 March 2014 19:26, Henry Saputra henry.sapu...@gmail.com wrote: The ODF Toolkit website [1] does not indicate which ones are the mentors. Do you mind just listing them in this thread for quick FYI? The canonical location for podling status is here: http://incubator.apache.org/projects/odftoolkit.html The canonical location is actually in the podling metadata: See instructions at http://incubator.apache.org/facilities.html#metadata That generates the listing here: http://incubator.apache.org/projects/#odftoolkit and other places. Yes the manually-edited status pages should also correlate with that (and this one does): Mentors: Sam Ruby, Nick Burch, Yegor Kozlov -David Thanks, Henry [1] https://incubator.apache.org/odftoolkit/people.html - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: January 2014 Incubator report timeline
P. Taylor Goetz wrote: Hi Marvin, I dropped the ball and didn’t get the Storm report in. But I also noticed that Storm wasn’t included in the template for this month’s report. I’m assuming that was just an oversight, correct? But Storm is not due to report: http://incubator.apache.org/facilities.html#report-schedule -David I imagine it’s too late for this month and that we should just report next month, but I’d be willing to put together a report tonight if it would be of any value. Thanks, Taylor - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Permission to edit wiki
Rhys Ulerich wrote: May I please have access to http://wiki.apache.org/incubator so I might edit the content for the log4cxx2 podling? My name there is 'RhysUlerich'. Done. -David Thank you, Rhys - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: January 2014 Incubator report timeline
John D. Ament wrote: Hi David, How often is clutch rerun? Thanks for your interest. It is run manually. See some notes: [1] http://incubator.apache.org/clutch.html#notes [2] http://incubator.apache.org/facilities.html#clutch Occasionally people do it immediately after some known changes. I try to ensure that it is run at least every couple of days. DeltaSpike should be cleared off the list :-) (assuming I did it right) I now added some notes to [2] to explain that there is a list of Incubator releases generated by cron on people.a.o as ~crossley twice per day. So the next run of Clutch would reflect any changes there. -David David Crossley wrote: Dave Fisher wrote: On Dec 25, 2013, at 5:22 PM, Roman Shaposhnik wrote: January 2014 Incubator report timeline: http://wiki.apache.org/incubator/January2014 FYI - Helix has graduated so I have removed it from the report. In the interests of the whole Incubator would Helix, and other graduated projects, please tidy up. There are some hints about the graduation process here: http://incubator.apache.org/clutch.html#other -David Regards, Dave Wed January 01 -- Podling reports due by end of day Sun January 05 -- Shepherd reviews due by end of day Sun January 05 -- Summary due by end of day Tue January 07 -- Mentor signoff due by end of day Wed January 08 -- Report submitted to Board Wed January 15 -- Board meeting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: January 2014 Incubator report timeline
John D. Ament wrote: Hi, Just an FYI, BatchEE did not receive a notice from Marvin. Should we change their reporting group? I now investigated their settings in content/podlings.xml The reporting stuff seems okay, monthly for the first three months.. They are correctly in this month's generated list at http://incubator.apache.org/report_due_3.txt Perhaps the message from marvin is being held up by their dev list moderation. Would someone please check, so that it does not happen again next month. They also need to manage their entry. I see some fixme notes about other stuff in there and some of it is a bit mangled. Which is why they are being listed at http://incubator.apache.org/clutch.html#other See: http://incubator.apache.org/facilities.html#metadata -David I'll separate email the dev list to notify them of the expected report. John On Wed, Dec 25, 2013 at 8:22 PM, Roman Shaposhnik r...@apache.org wrote: January 2014 Incubator report timeline: http://wiki.apache.org/incubator/January2014 Wed January 01 -- Podling reports due by end of day Sun January 05 -- Shepherd reviews due by end of day Sun January 05 -- Summary due by end of day Tue January 07 -- Mentor signoff due by end of day Wed January 08 -- Report submitted to Board Wed January 15 -- Board meeting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: January 2014 Incubator report timeline
Dave Fisher wrote: On Dec 25, 2013, at 5:22 PM, Roman Shaposhnik wrote: January 2014 Incubator report timeline: http://wiki.apache.org/incubator/January2014 FYI - Helix has graduated so I have removed it from the report. In the interests of the whole Incubator would Helix, and other graduated projects, please tidy up. There are some hints about the graduation process here: http://incubator.apache.org/clutch.html#other -David Regards, Dave Wed January 01 -- Podling reports due by end of day Sun January 05 -- Shepherd reviews due by end of day Sun January 05 -- Summary due by end of day Tue January 07 -- Mentor signoff due by end of day Wed January 08 -- Report submitted to Board Wed January 15 -- Board meeting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: permission to edit wiki
Done. -David Neng Geng Huang wrote: Hi! I would like to add something to the wiki, can I please have access? My login name is Neng Geng Huang Thanks! Huang -- -- Mr. Huang Neng Geng -- Associate Professor School of the Internet of Things Wuxi Institute of Technology Wuxi, Jiangsu, China, 214121 Mobile: 86-13921501950 email: huan...@gmail.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Question about jar files in svn.
Marvin Humphrey wrote: Greg Trasuk wrote: Thanks everyone for the input. To summarize, it appears that the consensus argument is: - Jar files are not prohibited by policy in project repositories (svn), although they may not make a lot of sense. - Source distributions must not distribute executable code in binary form. i.e. Don’t ship dependency jars in the source archive. However it may be acceptable to include things like jar files that are processed during testing (sample archives, for instance). - The project repositories are not generally considered “distributions”, but we need to be a little careful to avoid users’ confusion on this point. Regarding that last part, i reckon that is about: only referring the development community to the development resources and not instructing users to do that. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Release Verification Checklist
Marvin Humphrey wrote: ant elder wrote: All the stuff required to be checked when voting on a release should be documented in the ASF doc about releases. That its not in that doc suggests its not required. If someone thinks something is required then they should go get consensus around that with the wider ASF and get the ASF doc updated. There was a time not long ago, where hardly anything was documented. Rather it was just common-sense. So in my opinion, not being in those docs does not mean that it is not required. (Not sure where to insert some other comments in this thread, so will just dump them here.) I am concerned about potentially changing the way we do things. So, two comments with that in mind: Votes should also encourage anyone to vote (though of course as non-binding). With this SVN based technique, how do they do that? The current new guides/release.html says contains a link URL for the Manifest. I suppose that they could be encouraged to copy the text from SVN and reply via the dev mail list. If the dev list PPMC vote passes including 3+ IPMC members then there is no need for this second vote. The wording gives a slight twist which might sway the understanding of why we do such things. Also some good stuff is in the old guides/releasemanagement.html so we do need to ensure that is over at a.o/dev/. -David OK, I've done the research and I've migrated the manifest proposal to a new documentation page with the links. The ReleaseChecklist wiki page is now a home for optional checklist items. http://incubator.apache.org/guides/release.html https://wiki.apache.org/incubator/ReleaseChecklist Applying your criteria to the current checklist has resulted in the migration of two items to the optional list: * Each expanded source archive matches the corresponding SCM tag. It turns out the only place matching the SCM tag was documented is the Incubator's Release Management guide. Here's Leo Simons making the case against: http://markmail.org/message/2ncepopzgnshtyd6. * Build instructions are provided, unless obvious I haven't found any documentation that this is required anywhere on www.apache.org/dev or www.apache.org/legal. Bertrand, between me arguing that this won't come into play often enough and Ant and Olivier arguing that we should only include blockers documented elsewhere, I've made the judgment call that this should be moved to the optional list as well. Please let us know if you object. Podling releases are not quite the same as TLP releases, thats why they have the DISCLAIMER and incubating naming. I think we should be making it easier for podlings to do releases, if its really necessary then make an audit of the last release a requirement of graduation. I am passionately committed to making it easier for podlings to release, by granting limited self-governance to those who earn it. The proposal under consideration is a win for *both* streamlining the release voting process and improving release oversight. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: permission to edit wiki
I added that. -David Matthew Hayes wrote: Hi I would like to add something to the wiki, can I please have access? My login name is Matthew Hayes. Thanks! Matt - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Subscribtion at the private list
Raphael Bircher wrote: Hi all I'm still not subscribed at the private incubator list. I was sending a request, but for some reasons, I'm not registred yet. Can someone help me to get on the private list. Thanks! Gee, that is not good. If you still get no result, perhaps try contacting the moderators directly at private-owner@i.a.o -David Greetings Raphael - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Enable Release Checklist Experiment
Marvin Humphrey wrote: Please vote: [ ] +1 Yes, apply the patch enabling the experiment. [ ] -1 No, do not apply the patch enabling the experiment. Here is my +1 -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Changing moderation settings
Nathan Marz wrote: How can I change the moderation settings for the Storm user and dev lists? I'm getting enormous amounts of moderation emails (including lots triggered by JIRA). Is there a way to whitelist accounts, turn off moderation, and/or approve in bulk (like via a web interface)? Some tips are at: http://apache.org/dev/#mail http://apache.org/dev/committers.html#mail-moderate -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: IP Clearance before releasing
ant elder wrote: Benson Margulies wrote: If we deleted every release from the main Foundation distro area that had some divergence from some policy, no matter how tiny, my suspicion is that the distro area would become rather sparse. Yes quite. And lets not forget how the rules keep changing eg not so long ago people were insisting that all sorts of stuff absolutely must be put in the NOTICE file where as now it absolutely must NOT be there, who know what it will be like next year. I disagree with that summary. The principles and constraints (not rules) do not keep changing. Instead it is that people seem to not understand those, and it takes time to weed out the misguided behaviours and documentation. -David And the Incubator _is_ different and does have different policy and rules, hence on occasion podlings being permitted to do releases which include GPL dependencies while Incubating and just fixing those up as a graduation requirement. ...ant - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Ripple reports
Marvin Humphrey wrote: Marvin Humphrey mar...@rectangular.com wrote: Christian Grobmeier grobme...@gmail.com wrote: i just added the ripple report for december (its the same as november). We were to late in november. however the report template generator didn't include us in generation. OK, I see what happened. Ripple received reminders on ripple-dev on November 22 and November 28 insisting that Ripple needed to file a December2013 report. This happened because at the time, Ripple still had the monthly tag in podlings.xml. Part of the Chair's workflow is to remove expired monthly attributes from podlings.xml. I didn't get to that until shortly after the November 28 reminders were sent out. In all of the documentation and tools, i have been trying to encourage the podlings to look after their own metadata. Sure, we do seem to need a backstop, but please can we continue to encourage them to look after their own stuff. -David https://svn.apache.org/viewvc/incubator/public/trunk/content/podlings.xml?r1=1545305r2=1546281 Probably the best way to prevent this from happening in the future is to move this Chair task (along with a few others like creating the wiki template) to just after filing the last report. I can do that by rejiggering the blocks in report_runbook.py. Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [ANNOUNCE] Raphael Bircher joins the Incubator PMC
Raphael Bircher wrote: Am 27.11.13 20:57, schrieb Marvin Humphrey: Greetings, The Incubator PMC has voted to offer membership to Raphael Bircher and he has accepted. In addition to his work here in the Incubator, Raphael is active in Apache OpenOffice. Thanks again. Thanks to all who voted. Question... I have now to sing up at priv...@i.a.org. Do I have to do this by my self, or someone put me on this list. You can subscribe yourself. The moderators know you. -David Thank you, Raphael, for your work so far as a shepherd, and for hitting the ground running as an IPMC member by signing up as Mentor for the NPanday podling. And don't forget, we still missing one mentor ;-) Greetings Raphael - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Release Verification Checklist
Marvin Humphrey wrote: In response to Bertrand's proposal at http://s.apache.org/awz, I've created a draft release verification checklist: http://wiki.apache.org/incubator/ReleaseChecklist Thnaks for your huge efforts Marvin. [ ] Incubation disclaimer is present and correct. There is also the naming of the release, which must have incubating in its name. As Clutch tries to report, many projects neglect that. Perhaps change that item to either: [ ] Incubation disclaimers are present and correct. or [ ] Incubation disclaimer is correct and filename includes incubating. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] helix-0.6.2-incubating
David Nalley wrote: (and incidentally you don't seem to be moving older versions (0.6.0, 0.6.1, etc) to the archive when promoting a new release. - see http://www.apache.org/dev/release.html#when-to-archive for more) Anything that is in the dist area is automatically archived, as explained in that document. What they do need to do, is to *delete* all of the old releases from their dist area. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Transition Incubator dist area
On Nov 20, 2013 Marvin Humphrey wrote: On Nov 18, 2013 Marvin Humphrey wrote: If I've done everything right, it should be possible for Infra to flip the switch and use new-style dist.apache.org synchronization at the incubator/ level. Infra flipped the switch today. We now use dist.apache.org exclusively. It would be nice if we continue on with the cleanup. These tasks remain to be done. Marvin Humphrey The following run of Clutch reported somthing strange. Back in September 2013 the Ctakes project did clean up their distribution area: http://svn.apache.org/r1523922 However Clutch now reported that they need to clean up again. So their artefacts must have returned. http://svn.apache.org/r1544987 see the changes to content/clutcho2.ent file. So perhaps that is a sign of something. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Retire the Provisionr podling
Andrei Savu wrote: Hi - We voted [1] to retire the Provisionr podling form the Apache Incubator. Following the retirement guide, it is now time for an IPMC vote to ratify the decision. [ ] +1 Retire the Provisionr podling [ ] +0 Neither here nor there [ ] -1 Do not retire the podling because ... This vote will remain open for at least the next 72 hours. So far we've got 2 votes from IPMC members (not counting my own): I don't understand why yours would not be counted. And that makes 3. -David * Roman Shaposhnik * Tom White Thanks! [1] http://s.apache.org/xtG [2] http://incubator.apache.org/guides/retirement.html - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Majority vs Lazy Majority
Bertrand Delacretaz wrote: On Fri, Nov 15, 2013 at 4:03 PM, sebb seb...@gmail.com wrote: On 9 November 2013 12:17, Justin Mclean jus...@classsoftware.com wrote: ... My guess is that Lazy Majority is used because Majority implies more than 50% of possible voters need to vote. My guess is that it is a misprint for Lazy Consensus I'd say so - lazy majority is mentioned at http://ant.apache.org/bylaws.html but I didn't know there was such a concept in our projects. Many projects use it. See this Google search: site:apache.org Lazy Majority We use it at Forrest: http://forrest.apache.org/guidelines.html Ant was one of the projects at the time that we based ours on. -David I'd rather keep it simple and avoid mentioning it in the incubator docs. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: INFRA-6774
Jordan Zimmerman wrote: Can someone please explain to me what I need to do to have curator.incubator.apache.org redirect to curator.apache.org? You asked this a few hours ago on infrastructure@ and were given complete and additional answers by various separate people. Now you have more people at infra involved in the same stuff. And now expaned to include all of Incubator. What is up?. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: INFRA-6774
David Crossley wrote: Jordan Zimmerman wrote: Can someone please explain to me what I need to do to have curator.incubator.apache.org redirect to curator.apache.org? You asked this a few hours ago on infrastructure@ and were given complete and additional answers by various separate people. Now you have more people at infra involved in the same stuff. And now expaned to include all of Incubator. What is up?. Ah, i was answering from the infrastructure@ list. Now i see additional information about svn access in the Incubator thread. However, your question above seemed to be a repeat. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: INFRA-6774
Jordan Zimmerman wrote:
When I tried to commit the change, I get:
svn: E175013: Commit failed (details follow):
svn: E175013: Access to '/repos/asf/!svn/me' forbidden
Are you able to commit to other stuff?
e.g. your podling status page
or to podlings.xml file.
You would have had that access while you were in
the Incubator and should still have it AFAIK.
How are you doing this process?
e.g. via the CMS
or via svn checkout on your workstation
or ...
-David
On Nov 19, 2013, at 7:49 PM, Jake Farrell jfarr...@apache.org wrote:
Please follow the incubation graduation guide
http://incubator.apache.org/guides/graduation.html see the Transferring
resources #3.2 user Websites
Websites
Transfer the podling website
Load the website into its new home. See infra notes.
Update the incubator/site-publish/.htaccess entry to redirect traffic from
the old URLs to the new. (svn location is
athttp://svn.apache.org/repos/asf/incubator/public/trunk/content/.htaccess)
Delete the podling website from
/www/incubator.apache.org/content/${podling-name} on people.apache.org if
possible. It won't be possible to remove the ${podling-name} directory
(because incubator uses svnpubsub). If the podling also used svnpubsub it
won't be possible to delete the files either. File a JIRA ticket under
INFRA and ask for the remains to be removed.
Post an announcement to user and development lists
When using Maven: update pom.xml for the location of the website, as well
as the place where the site plugin will deploy the web site (when
applicable).
-Jake
On Tue, Nov 19, 2013 at 10:40 PM, Jordan Zimmerman randg...@apache.org
wrote:
Can someone please explain to me what I need to do to have
curator.incubator.apache.org redirect to curator.apache.org?
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: INFRA-6774
Joseph Schaefer wrote: No there’s a difference. Before he was asking what infra was going to do to magically make this happen. That request was denied. Now we have a better question: what can he do himself to make this happen? Here there are some answers to questions that should be addressed in the incubator docs but aren’t, because this particular website graduation is OUTSIDE of the typical incubator.apache.org/foo sub site. Technically this is a non-event by design from infra’s standpoint because once DNS is enabled we have done all we need to do to start serving up the new traffic, other than capture any site source relocations in our svnpubsub config file. All a project like curator needs to do now is add an appropriate .htaccess file to the top-level of their site with the two RewriteCond / RewriteRule directives to move traffic away from their incubator subdomain and to their top-level domain. Would someone please merge Joe and the following docs so we can get out of these loops. Jake Farrell wrote: Please follow the incubation graduation guide http://incubator.apache.org/guides/graduation.html see the Transferring resources #3.2 user Website Thank you! One wonders why projects are not following these guides. There is also clear direction here: http://www.apache.org/dev/infra-contact#requesting-graduation -David David Crossley wrote: David Crossley wrote: Jordan Zimmerman wrote: Can someone please explain to me what I need to do to have curator.incubator.apache.org redirect to curator.apache.org? You asked this a few hours ago on infrastructure@ and were given complete and additional answers by various separate people. Now you have more people at infra involved in the same stuff. And now expaned to include all of Incubator. What is up?. Ah, i was answering from the infrastructure@ list. Now i see additional information about svn access in the Incubator thread. However, your question above seemed to be a repeat. -David - 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: INFRA-6774
Joseph Schaefer wrote:
Already resolved. A Forbidden response instead
of a failed auth request almost always implies
committing using http.
Great, thanks for following up.
What a committer trap that one is.
A while ago we added that to the FAQ:
Google: site:apache.org/dev committer https
http://www.apache.org/dev/committers.html#commit-403
(although that seems to use old terminology).
http://www.apache.org/dev/version-control.html#https-svn
Would someone please clarify the docs.
-David
David Crossley wrote:
Jordan Zimmerman wrote:
When I tried to commit the change, I get:
svn: E175013: Commit failed (details follow):
svn: E175013: Access to '/repos/asf/!svn/me' forbidden
Are you able to commit to other stuff?
e.g. your podling status page
or to podlings.xml file.
You would have had that access while you were in
the Incubator and should still have it AFAIK.
How are you doing this process?
e.g. via the CMS
or via svn checkout on your workstation
or ...
-David
On Nov 19, 2013, at 7:49 PM, Jake Farrell jfarr...@apache.org wrote:
Please follow the incubation graduation guide
http://incubator.apache.org/guides/graduation.html see the Transferring
resources #3.2 user Websites
Websites
Transfer the podling website
Load the website into its new home. See infra notes.
Update the incubator/site-publish/.htaccess entry to redirect traffic
from the old URLs to the new. (svn location is
athttp://svn.apache.org/repos/asf/incubator/public/trunk/content/.htaccess)
Delete the podling website from
/www/incubator.apache.org/content/${podling-name} on people.apache.org if
possible. It won't be possible to remove the ${podling-name} directory
(because incubator uses svnpubsub). If the podling also used svnpubsub it
won't be possible to delete the files either. File a JIRA ticket under
INFRA and ask for the remains to be removed.
Post an announcement to user and development lists
When using Maven: update pom.xml for the location of the website, as well
as the place where the site plugin will deploy the web site (when
applicable).
-Jake
On Tue, Nov 19, 2013 at 10:40 PM, Jordan Zimmerman randg...@apache.org
wrote:
Can someone please explain to me what I need to do to have
curator.incubator.apache.org redirect to curator.apache.org?
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
Re: Transition Incubator dist area
Marvin Humphrey wrote: Hello general@incubator, Infra has requested that we perform some cleanup of our distribution area. Earlier this week, both Allura and VXQuery experienced difficulties with synchronization between their dist.apache.org release directories and the main mirror at http://www.apache.org/dist/. This is happening because the `incubator` dist directory is a hodgepodge of old-style and new-style distribution. To see what needs to be fixed, log into people.apache.org and examine the output of `ls -l /dist/incubator/`. Here's an excerpt: drwxrwxr-x 3 svnwc svnwc10 Nov 16 18:02 allura drwxrwsr-x 10 omalleyincubator12 Oct 21 16:53 ambari drwxrwsr-x 4 simonetripodi incubator 5 Jul 29 2012 amber drwxrwxr-x 4 svnwc svnwc 5 Nov 16 18:04 blur Any directory which has the group `incubator` needs to be transitioned, which involves copying the `$PODLING` directory and everything in it to `https://dist.apache.org/repos/dist/release/incubator/$PODLING`. (The `ambari` and `amber` directories would need to be copied, but the `allura` and `blur` directories would not). Once everything is transitioned, Infra will flip the switch and everybody in the Incubator will use new-style `dist.apache.org` distribution henceforth. For the sake of simplicity, it would be better if we could get a single volunteer to take on this task. Since every Incubator committer has rights to all of `https://dist.apache.org/repos/dist/release/incubator/`, you don't have to be an IPMC member. Any takers? Marvin Humphrey Thanks for setting such a thorough foundation. I cannot be that person, but i will be able to assist with answering queries and with observations. One thing that would help is to also clear the clutter. Clutch has been alerting to old releases hanging around. http://incubator.apache.org/clutch.html#other There are many in that list with the entry: Has graduated, but still has remains on Incubator distribution mirrors. Yes, i know that a proportion will have not yet made a release as the new TLP. They would remain as reminders. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: the Voting Status monitor is overloaded
Lahiru Sandaruwan wrote: Release Apache Stratos 3.0.0 Incubating RC4 Will send the result correctly again. Thanks. Cleared now. They added (passed) at the end of Subject. FIXME: perhaps voter/voter.py needs additional code to handle such -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: the Voting Status monitor is overloaded
Thanks to those who did follow-up. That clears a bit. Another plea from me to help you to clear the clutter: I reviewed the mail archives for the outstanding ones to see why the Vote Monitor did not detect their vote result. I do not have time to correct them nor to tweak voter.py but hope that others can utilise my work. Here is a summary: As expected in my original mail, some tallies added extra words to the Subject, so tricked the monitor. Others did not tally. Others tallied but did not add RESULT tag. Others did cancel but did not add CANCEL tag. There were a few community graduation votes which were Fwd: but did not summarise. Perhaps voter.py could detect these notices. There were a few with common mis-spelings, such as the CANCLE one. Thanks to Branko, the regex is nice. People could help to expand. Some possible tweaks to voter/voter.py are flagged below. Some situations could be cleared with a new RESULT or CANCEL email. Please assist. Notes: Release Apache Stratos 3.0.0 Incubating RC4 They added (passed) at the end of Subject. Release Apache Tajo-0.2-incubating RC1 Prepended tag CANCLE instead. (FIXME: voter/voter.py needs additional code to handle such typo errors.) (Now a follow-up has done a reply with CANCEL.) Apache Ambari 1.4.1-incubating RC1 No-one did summarise. Graduate Apache Marmotta from incubator and become a TLP This was a community graduation vote. Used Fwd: but not summarised. (FIXME: perhaps voter/voter.py needs additional code to handle such notices.) Apache Kalumet 0.6-incubating release (3rd try) No-one did summarise. Usergrid BaaS Stack for Apache Incubator No-one did CANCEL. (A subsequent new thread was summarised, but this old one remains.) : Release Apache Sentry 1.2.0 incubating (rc0) Was tallied but no RESULT tag. Apache Chukwa graduation Was tallied and RESULT, but different thread with different Subject. first milestone release of Apache Drill (incubating) Was tallied, but broke the thread and removed the VOTE tag. Graduate Curator from Apache Incubator This was a community graduation vote. Used Fwd: but not summarised. (FIXME: perhaps voter/voter.py needs additional code to handle such notices.) Release Apache Provisionr version 0.4.0-incubating, RC0 Was tallied and RESULT, but different thread with different Subject. Release Curator 2.1.0-incubating No-one did summarise. Release Apache Wave 0.4 based on RC3 No-one did summarise. Accept Stratos proposal as an incubating project Was tallied, and RESULT tag but had Re: in between the tags 2013-06-20 (FIXME: voter/voter.py needs additional code to handle this.) Accept Apache BeanShell in the Incubator No-one did summarise. Release Apache Mesos 0.11.0-incubating (RC1) No-one did tag with CANCEL helix 0.6.1-incubating Was tallied and RESULT, but different thread with different Subject. S4 0.6.0 Release Candidate 4 No-one did summarise. S4 0.6.0 Incubating Release Candidate 3 No-one did tag with CANCEL. Recommending DeltaSpike for Graduation to an Apache Top Level Project This was a community graduation vote. Used Fwd: but not summarised. (FIXME: perhaps voter/voter.py needs additional code to handle such notices.) --- David Crossley wrote: If the projects that are listed there cannot make the effort to clean up, then do not be surpised if your subsequent vote threads are overlooked. This is also not fair on the other projects, especially new ones. -David David Crossley wrote: It seems that the brilliant Voting Status monitor has fallen into disrepair. Partly due to people not properly following up with a clear RESULT tally and partly perhaps inadequacies of the monitor script. Follow the top-left link from the Incubator home: http://incubator.apache.org/ Items coloured any shade of orange need attention. We all need to care for these tools to assist us through incubation efficiently. Would people who have an interest in each open entry please review the email archives to see why your result summary tally email was not detected. Perhaps you forgot to prepend [RESULT]. Or maybe changed the email Subject too and so confused the monitor. If so then please send a followup to your VOTE thread. That will cause the monitor to clear its backlog. However, i do see some that should be marked as Resolved. So maybe the script that does this scan needs tweaks to pattern matching. The code is there for all in the top-level of Incubator SVN. http://incubator.apache.org/facilities.html#voting-status Please add more instructions to the docs: http://incubator.apache.org/facilities.html#voting-status -David
Re: [DISCUSS] Apache Ambari Graduation Resolution Draft
I compared the text of your resolution to that of the template. All appears to be okay. Good to see a solid number of people on your initial PMC. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Graduate Apache Marmotta as TLP
Jakob Frank wrote: Hi all, the Marmotta podling, whose goal is to provide an Open Platform for Linked Data, entered incubation in December 2012. Since then, the codebase has stabilized and two releases were published following ASF policies and guidelines. The community has grown, two new committers have joined the development team and more people joined the mailing lists. The last incubator report lists Marmotta as Ready to graduate [1], the Marmotta community has decided to take this step [2] and agreed on a Graduation Resolution Draft [3] which is also attached below. In my opinion, it is not a good idea to remove the clause about bylaws. That takes away your project's power. Just create a simple guidelines (== bylaws) page that says you follow the Apache HTTP Server project for example. -David The resolution draft was posted to general@incubator.a.o for discussion [4] and raised no concerns, now please cast your votes: [ ] +1 Graduate the Marmotta podling from Incubator [ ] +0 Indifferent to graduation status of the Marmotta podling [ ] -1 Reject graduation of the Marmotta podling from Incubator because... The vote will be open for at least 72 hours starting now. Best, Jakob on behalf of the Marmotta community [1] http://s.apache.org/marmotta-graduation-vote [2] http://s.apache.org/marmotta-graduation-result [3] http://s.apache.org/marmotta-graduation-resolution [4] http://s.apache.org/dYt Apache Marmotta Graduation Resolution = X. Establish the Apache Marmotta Project WHEREAS, the Board of Directors deems it to be in the best interests of the Foundation and consistent with the Foundation's purpose to establish a Project Management Committee charged with the creation and maintenance of open-source software, for distribution at no charge to the public, related to an open platform for Linked Data. NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee (PMC), to be known as the Apache Marmotta Project, be and hereby is established pursuant to Bylaws of the Foundation; and be it further RESOLVED, that the Apache Marmotta Project be and hereby is responsible for the creation and maintenance of software related to an open platform for Linked Data; and be it further RESOLVED, that the office of Vice President, Apache Marmotta be and hereby is created, the person holding such office to serve at the direction of the Board of Directors as the chair of the Apache Marmotta Project, and to have primary responsibility for management of the projects within the scope of responsibility of the Apache Marmotta Project; and be it further RESOLVED, that the persons listed immediately below be and hereby are appointed to serve as the initial members of the Apache Marmotta Project: * Peter Ansell ans...@apache.org * Fabian Christ fchr...@apache.org * Sergio Fernández wik...@apache.org * Jakob Frank ja...@apache.org * Dietmar Glachs dgla...@apache.org * Thomas Kurz tk...@apache.org * Nandana Mihindukulasooriya nand...@apache.org * Raffaele Palmieri rpalmi...@apache.org * Sebastian Schaffert sschaff...@apache.org * Rupert Westenthaler rwes...@apache.org NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jakob Frank be appointed to the office of Vice President, Apache Marmotta, to serve in accordance with and subject to the direction of the Board of Directors and the Bylaws of the Foundation until death, resignation, retirement, removal or disqualification, or until a successor is appointed; and be it further RESOLVED, that the Apache Marmotta Project be and hereby is tasked with the migration and rationalization of the Apache Incubator Marmotta podling; and be it further RESOLVED, that all responsibilities pertaining to the Apache Incubator Marmotta podling encumbered upon the Apache Incubator Project are hereafter discharged. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Shepherding November 2013
John D. Ament wrote: Hi Marvin, Can anyone volunteer? Or only IPMC? I'd like to volunteer to help you guys out next month. Anyone can. Please. I gather that you just need to add/maintain this file: https://svn.apache.org/repos/asf/incubator/public/trunk/content/shepherds.json -David John - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Shepherding November 2013
Andrei Savu wrote: Something is fishy. I haven't received any Shepherd assignments ... email for November and I've done no reviews. It's not clear to me how my name got added as a reviewer for Tez. Dunno about email. I added a section to explain the process a bit: http://incubator.apache.org/facilities.html#shepherds So you were assigned to Tez by the script. Regarding the edits, my local 'mairix' search found this: https://wiki.apache.org/incubator/November2013?action=diffrev1=26rev2=27 -David On Mon, Nov 11, 2013 at 3:04 PM, Marvin Humphrey mar...@rectangular.comwrote: Shepherd reviews extracted from https://wiki.apache.org/incubator/November2013: Ambari Roman Shaposhnik (rvs): Project should be pretty close to a well deserved graduation. Kudos to the community building effort! BatchEE Suresh Marru (smarru): The podling is waiting on website setup. The dev mailing list is not yet setup (or atleast not visible in archives), surprisingly the user and commit lists have archives, is something amiss? Blur Suresh Marru (smarru): * The podling seems to be very healthy and kudos to PPMC for pulling of their first release and getting ready for second. * A big kudos to couple of mentors for pro-actively engaging. * Blur website does not conform to the branding guidelines and should add the incubator logo and disclaimer prominently. Also, should include the ASF, security and thanks to sponsor links. Sirona Roman Shaposhnik (rvs): Given that it has been less then a month since project entered incubation I see that the most immediate needs of having a source code repo, JIRA and MLs have been met. Still it would be nice if the bootstrapping were to wrap up as quickly as possible. At this point, for example, there's no website and no wiki, etc. Those are the tools for helping the community growth and it would be very nice to see those coming online in a few weeks. Tez Andrei Savu (asavu): The project is moving very quickly, but needs to make a release soon. Podlings which did not receive shepherd reviews this cycle: Aurora DeviceMap Droids Hadoop Development Tools Knox Open Climate Workbench Ripple Sentry Storm - 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: projects graduated need to tidy up
Jake Farrell wrote: I've started to clean up the voter status page and have been finishing the incubator closing steps for projects that have already graduated. Updates for the projects listed below should start appearing shortly as the nightly scripts run. Hopefully these steps will make it easier for the tools to function as intended Do the instructions need some tweaking to explain that the enddate needs to be added for each? -David Chukwa, DeltaSpike, jclouds, Tashi -Jake On Thu, Nov 7, 2013 at 5:45 PM, David Crossley cross...@apache.org wrote: John D. Ament wrote: David, On that note, how come DeltaSpike is still listed as incubating at [1] Note the table on the 3rd bullet. [1]: http://incubator.apache.org/ Because these graduated projects do not tidy up after themselves. They seem to leave everything for other Incubator volunteers to clean up in their wake. Such a mess causes the Incubator tools, that try so hard to help us all, to become overloaded and then not as useful because there is too much fluff. DeltaSpike is not the only one. See the list that poor Clutch tries so desperately to highlight: http://incubator.apache.org/clutch.html#other which also attempts to directly link them to the relevant docs. The projects listing http://incubator.apache.org/projects/ also tries to encourage projects to maintain their own records. I presume that these projects will continue such behaviour as TLPs. (Sorry if i come across as frustrated in these threads. I certainly am, but trying to curb it.) -David On Thu, Nov 7, 2013 at 5:23 PM, David Crossley cross...@apache.org wrote: David Crossley wrote: Romain Manni-Bucau wrote: Hi David not sure what you mean but list are working AFAIK. We got batchee mail this morning again and I got some sirona mails yesterday The archives. Clutch gathers the mail list addresses by ensuring that the archives are available [1]. See the URL provided below in my initial email. e.g. http://mail-archives.apache.org/mod_mbox/#batchee.incubator There is only the commits archives. Someone from these two projects needs to follow up with Infra until your resources are properly established. And this is why you are not receiving the report reminders. [1] We should enhance this page to explain more detail about how the set of reporting mailing list addresses are handled. I have explained it many times in email, so we should find that and add it to this doc. http://incubator.apache.org/facilities.html#reminders The Voting Status monitor (the poor neglected thing!) has also been trying to warn about this issue. See the top-left of http://incubator.apache.org/ and then the bottom table. -David Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/11/7 David Crossley cross...@apache.org: Those two reminders are intended for BatchEE and Sirona. Their email dev list archive is not yet available, so this goes to general@ list. Clutch does detect their commits lists, but not their dev lists. http://mail-archives.apache.org/mod_mbox/#batchee.incubator http://mail-archives.apache.org/mod_mbox/#sirona.incubator Does anyone know why? Are they missing moderators or something? -David - 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: projects graduated need to tidy up
David Crossley wrote: Jake Farrell wrote: I've started to clean up the voter status page ... Thanks. Let us hope that that enourages podlings to continue to follow through. ... and have been finishing the incubator closing steps for projects that have already graduated. However this finalisation stuff is difficult if one was not associated with the project. Tweaking the podlings.xml is just one very final step. I usually leave it there as a sign that there is stuff to be done. Updates for the projects listed below should start appearing shortly as the nightly scripts run. Hopefully these steps will make it easier for the tools to function as intended For the Vote Monitor yes, as it is completely overloaded. For Clutch (not automated) it is doing is intended job. The History chart is automated, but i wonder if it skipped two becuase of the problem below. Do the instructions need some tweaking to explain that the enddate needs to be added for each? The tools are crude and do not expect partial information. Please do follow the instructions, and if they are not clear then help to refine. -David Chukwa, DeltaSpike, jclouds, Tashi -Jake - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [PROPOSAL] Weave for Apache Incubator
Andreas Neumann wrote: Thank you for the feedback, it looks like the name Twill is appealing enough. I will update the proposal with the new name. I would also like to put the proposal on the incubator wiki (at https://wiki.apache.org/incubator/TwillProposal), can you please give me the privileges? (my user name is AndreasNeumann) Added you to ContributorsGroup. -David Thanks, -Andreas. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
missing dev mail list for BatchEE and Sirona
Those two reminders are intended for BatchEE and Sirona. Their email dev list archive is not yet available, so this goes to general@ list. Clutch does detect their commits lists, but not their dev lists. http://mail-archives.apache.org/mod_mbox/#batchee.incubator http://mail-archives.apache.org/mod_mbox/#sirona.incubator Does anyone know why? Are they missing moderators or something? -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: missing dev mail list for BatchEE and Sirona
Romain Manni-Bucau wrote: Hi David not sure what you mean but list are working AFAIK. We got batchee mail this morning again and I got some sirona mails yesterday The archives. Clutch gathers the mail list addresses by ensuring that the archives are available [1]. See the URL provided below in my initial email. e.g. http://mail-archives.apache.org/mod_mbox/#batchee.incubator There is only the commits archives. Someone from these two projects needs to follow up with Infra until your resources are properly established. And this is why you are not receiving the report reminders. [1] We should enhance this page to explain more detail about how the set of reporting mailing list addresses are handled. I have explained it many times in email, so we should find that and add it to this doc. http://incubator.apache.org/facilities.html#reminders -David Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/11/7 David Crossley cross...@apache.org: Those two reminders are intended for BatchEE and Sirona. Their email dev list archive is not yet available, so this goes to general@ list. Clutch does detect their commits lists, but not their dev lists. http://mail-archives.apache.org/mod_mbox/#batchee.incubator http://mail-archives.apache.org/mod_mbox/#sirona.incubator Does anyone know why? Are they missing moderators or something? -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: missing dev mail list for BatchEE and Sirona
David Crossley wrote: Romain Manni-Bucau wrote: Hi David not sure what you mean but list are working AFAIK. We got batchee mail this morning again and I got some sirona mails yesterday The archives. Clutch gathers the mail list addresses by ensuring that the archives are available [1]. See the URL provided below in my initial email. e.g. http://mail-archives.apache.org/mod_mbox/#batchee.incubator There is only the commits archives. Someone from these two projects needs to follow up with Infra until your resources are properly established. And this is why you are not receiving the report reminders. [1] We should enhance this page to explain more detail about how the set of reporting mailing list addresses are handled. I have explained it many times in email, so we should find that and add it to this doc. http://incubator.apache.org/facilities.html#reminders The Voting Status monitor (the poor neglected thing!) has also been trying to warn about this issue. See the top-left of http://incubator.apache.org/ and then the bottom table. -David Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/11/7 David Crossley cross...@apache.org: Those two reminders are intended for BatchEE and Sirona. Their email dev list archive is not yet available, so this goes to general@ list. Clutch does detect their commits lists, but not their dev lists. http://mail-archives.apache.org/mod_mbox/#batchee.incubator http://mail-archives.apache.org/mod_mbox/#sirona.incubator Does anyone know why? Are they missing moderators or something? -David - 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
projects graduated need to tidy up
John D. Ament wrote: David, On that note, how come DeltaSpike is still listed as incubating at [1] Note the table on the 3rd bullet. [1]: http://incubator.apache.org/ Because these graduated projects do not tidy up after themselves. They seem to leave everything for other Incubator volunteers to clean up in their wake. Such a mess causes the Incubator tools, that try so hard to help us all, to become overloaded and then not as useful because there is too much fluff. DeltaSpike is not the only one. See the list that poor Clutch tries so desperately to highlight: http://incubator.apache.org/clutch.html#other which also attempts to directly link them to the relevant docs. The projects listing http://incubator.apache.org/projects/ also tries to encourage projects to maintain their own records. I presume that these projects will continue such behaviour as TLPs. (Sorry if i come across as frustrated in these threads. I certainly am, but trying to curb it.) -David On Thu, Nov 7, 2013 at 5:23 PM, David Crossley cross...@apache.org wrote: David Crossley wrote: Romain Manni-Bucau wrote: Hi David not sure what you mean but list are working AFAIK. We got batchee mail this morning again and I got some sirona mails yesterday The archives. Clutch gathers the mail list addresses by ensuring that the archives are available [1]. See the URL provided below in my initial email. e.g. http://mail-archives.apache.org/mod_mbox/#batchee.incubator There is only the commits archives. Someone from these two projects needs to follow up with Infra until your resources are properly established. And this is why you are not receiving the report reminders. [1] We should enhance this page to explain more detail about how the set of reporting mailing list addresses are handled. I have explained it many times in email, so we should find that and add it to this doc. http://incubator.apache.org/facilities.html#reminders The Voting Status monitor (the poor neglected thing!) has also been trying to warn about this issue. See the top-left of http://incubator.apache.org/ and then the bottom table. -David Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/11/7 David Crossley cross...@apache.org: Those two reminders are intended for BatchEE and Sirona. Their email dev list archive is not yet available, so this goes to general@ list. Clutch does detect their commits lists, but not their dev lists. http://mail-archives.apache.org/mod_mbox/#batchee.incubator http://mail-archives.apache.org/mod_mbox/#sirona.incubator Does anyone know why? Are they missing moderators or something? -David - 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: the Voting Status monitor is overloaded
If the projects that are listed there cannot make the effort to clean up, then do not be surpised if your subsequent vote threads are overlooked. This is also not fair on the other projects, especially new ones. -David David Crossley wrote: It seems that the brilliant Voting Status monitor has fallen into disrepair. Partly due to people not properly following up with a clear RESULT tally and partly perhaps inadequacies of the monitor script. Follow the top-left link from the Incubator home: http://incubator.apache.org/ Items coloured any shade of orange need attention. We all need to care for these tools to assist us through incubation efficiently. Would people who have an interest in each open entry please review the email archives to see why your result summary tally email was not detected. Perhaps you forgot to prepend [RESULT]. Or maybe changed the email Subject too and so confused the monitor. If so then please send a followup to your VOTE thread. That will cause the monitor to clear its backlog. However, i do see some that should be marked as Resolved. So maybe the script that does this scan needs tweaks to pattern matching. The code is there for all in the top-level of Incubator SVN. http://incubator.apache.org/facilities.html#voting-status Please add more instructions to the docs: http://incubator.apache.org/facilities.html#voting-status -David - 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: projects graduated need to tidy up
John D. Ament wrote: Well, I can appreciate the frustration. I'm willing to help clean up some of this stuff. Any special rights required to edit podlings.xml? IIUC then everyone who comes through the Incubator is able: http://people.apache.org/committers-by-project.html#incubator -David On Thu, Nov 7, 2013 at 5:45 PM, David Crossley cross...@apache.org wrote: John D. Ament wrote: David, On that note, how come DeltaSpike is still listed as incubating at [1] Note the table on the 3rd bullet. [1]: http://incubator.apache.org/ Because these graduated projects do not tidy up after themselves. They seem to leave everything for other Incubator volunteers to clean up in their wake. Such a mess causes the Incubator tools, that try so hard to help us all, to become overloaded and then not as useful because there is too much fluff. DeltaSpike is not the only one. See the list that poor Clutch tries so desperately to highlight: http://incubator.apache.org/clutch.html#other which also attempts to directly link them to the relevant docs. The projects listing http://incubator.apache.org/projects/ also tries to encourage projects to maintain their own records. I presume that these projects will continue such behaviour as TLPs. (Sorry if i come across as frustrated in these threads. I certainly am, but trying to curb it.) -David On Thu, Nov 7, 2013 at 5:23 PM, David Crossley cross...@apache.org wrote: David Crossley wrote: Romain Manni-Bucau wrote: Hi David not sure what you mean but list are working AFAIK. We got batchee mail this morning again and I got some sirona mails yesterday The archives. Clutch gathers the mail list addresses by ensuring that the archives are available [1]. See the URL provided below in my initial email. e.g. http://mail-archives.apache.org/mod_mbox/#batchee.incubator There is only the commits archives. Someone from these two projects needs to follow up with Infra until your resources are properly established. And this is why you are not receiving the report reminders. [1] We should enhance this page to explain more detail about how the set of reporting mailing list addresses are handled. I have explained it many times in email, so we should find that and add it to this doc. http://incubator.apache.org/facilities.html#reminders The Voting Status monitor (the poor neglected thing!) has also been trying to warn about this issue. See the top-left of http://incubator.apache.org/ and then the bottom table. -David Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/11/7 David Crossley cross...@apache.org: Those two reminders are intended for BatchEE and Sirona. Their email dev list archive is not yet available, so this goes to general@ list. Clutch does detect their commits lists, but not their dev lists. http://mail-archives.apache.org/mod_mbox/#batchee.incubator http://mail-archives.apache.org/mod_mbox/#sirona.incubator Does anyone know why? Are they missing moderators or something? -David - 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: projects graduated need to tidy up
John D. Ament wrote: Well, must be missing something. I'm 'johndament' yet I don't have write access to the trunk. I used to understand svn auth, but not so sure now. Following this: http://incubator.apache.org/guides/mentor.html#who-auth-karma It seems to me that all in committers as well as all in the incubator group have rw access to incubator/public/trunk/ Do your fellow project committers also have this trouble? If so, i wonder if this identifies a problem which indicates why few people have edited podlings.xml or fix the website docs. If so, then i would be horrifed that they have not told us. -David On Thu, Nov 7, 2013 at 6:26 PM, David Crossley cross...@apache.org wrote: John D. Ament wrote: Well, I can appreciate the frustration. I'm willing to help clean up some of this stuff. Any special rights required to edit podlings.xml? IIUC then everyone who comes through the Incubator is able: http://people.apache.org/committers-by-project.html#incubator -David On Thu, Nov 7, 2013 at 5:45 PM, David Crossley cross...@apache.org wrote: John D. Ament wrote: David, On that note, how come DeltaSpike is still listed as incubating at [1] Note the table on the 3rd bullet. [1]: http://incubator.apache.org/ Because these graduated projects do not tidy up after themselves. They seem to leave everything for other Incubator volunteers to clean up in their wake. Such a mess causes the Incubator tools, that try so hard to help us all, to become overloaded and then not as useful because there is too much fluff. DeltaSpike is not the only one. See the list that poor Clutch tries so desperately to highlight: http://incubator.apache.org/clutch.html#other which also attempts to directly link them to the relevant docs. The projects listing http://incubator.apache.org/projects/ also tries to encourage projects to maintain their own records. I presume that these projects will continue such behaviour as TLPs. (Sorry if i come across as frustrated in these threads. I certainly am, but trying to curb it.) -David On Thu, Nov 7, 2013 at 5:23 PM, David Crossley cross...@apache.org wrote: David Crossley wrote: Romain Manni-Bucau wrote: Hi David not sure what you mean but list are working AFAIK. We got batchee mail this morning again and I got some sirona mails yesterday The archives. Clutch gathers the mail list addresses by ensuring that the archives are available [1]. See the URL provided below in my initial email. e.g. http://mail-archives.apache.org/mod_mbox/#batchee.incubator There is only the commits archives. Someone from these two projects needs to follow up with Infra until your resources are properly established. And this is why you are not receiving the report reminders. [1] We should enhance this page to explain more detail about how the set of reporting mailing list addresses are handled. I have explained it many times in email, so we should find that and add it to this doc. http://incubator.apache.org/facilities.html#reminders The Voting Status monitor (the poor neglected thing!) has also been trying to warn about this issue. See the top-left of http://incubator.apache.org/ and then the bottom table. -David Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2013/11/7 David Crossley cross...@apache.org: Those two reminders are intended for BatchEE and Sirona. Their email dev list archive is not yet available, so this goes to general@ list. Clutch does detect their commits lists, but not their dev lists. http://mail-archives.apache.org/mod_mbox/#batchee.incubator http://mail-archives.apache.org/mod_mbox/#sirona.incubator Does anyone know why? Are they missing moderators or something? -David - 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
Re: [IMO] There are no Incubator issues
Martijn Dashorst wrote: ... Well said. Hooray for common-sense and taking ownership. We must remember that we are all individuals. The ASF enables us to do what we want. We each need to take the initiative. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
who are your Mentors
I reckon that these lists are not complete. Would people from each podling review the generated lists at: http://incubator.apache.org/projects/ a list of all current podlings with Description and Mentors, etc. http://incubator.apache.org/clutch.html#mentors all people listed and their associated podlings. Remember that these are all generated from content/podlings.xml If projects feel that they need additional Mentors, then please arrange for that, and then keep that file up-to-date. Please. Also see http://incubator.apache.org/facilities.html -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Cultivating Outstanding IP Stewards
Upayavira wrote: I have one (hopefully) simple question for those more familiar with the ASF\s bylaws/etc. As I understand it, the board has delegated responsibility for the incubator, and thus incubator podlings, to the Incubator PMC and its members. Thus, it is only members of the Incubator PMC that have the ability to vote. This much is straight-forward. So, the question is, what options does the Incubator PMC have in terms of further delegating responsibility? Can the Incubator PMC delegate (some) responsibility to people who are not themselves incubator PMC members? To do so, does the Incubator PMC need to inform the board of the change of composition of 'sub-committees'? My thought is that if we can clarify what is legally possible, we will be better placed to find the appropriate model for the incubator that fits within those legal/bylaw bounds. I was wondering the same. This seems to enable such: RESOLVED, that the initial Apache Incubator PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Incubator Project. http://incubator.apache.org/official/resolution.html -David Upayavira On Fri, Nov 8, 2013, at 06:47 AM, Marvin Humphrey wrote: On Thu, Nov 7, 2013 at 11:29 AM, Jim Jagielski j...@jagunet.com wrote: Certainly this is being addressed and fixed in the current 1.0.1 release thread... Indeed. So why is something 2 months old such a bee in your bonnet right now? I chose to highlight the Allura situation because it illustrates that IPMC release vote scarcity can strike your podling at any time regardless of how virtuous and healthy it is. If it can happen to Allura, a podling with fabulous contributors and outrageously qualified Mentors, it can happen to anyone. I could have instead cited other lengthy release votes: VXQuery (over a month now and still waiting), ODF Toolkit (20 days), Droids (probably the all-time record holder), Bloodhound (so frustrating that Brane coded up the voting monitor), ManifoldCF... but none of those podlings boasted Allura's all-star Mentor lineup. The point was to pick a podling with Mentors whose dedication to the ASF was unassailable (AWOL Mentors don't attend Board meetings!) because then nobody could blame the delay on insufficient Mentor dedication. I don't think it's a bad thing that podling core developers are inherently more invested in their projects than Mentors -- it's just a fact of life that we ought to accommodate ourselves to. Vote scarcity is not the fault of any one Mentor, or any group of Mentors -- it's just a phenomenon which is *guaranteed* to happen some of the time because the Incubator is structurally flawed. Still, because my point was awkwardly crafted, I wound up singling out the Allura team in a negative context. I apologize for my clumsiness. 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: Cultivating Outstanding IP Stewards
David Crossley wrote: Upayavira wrote: I have one (hopefully) simple question for those more familiar with the ASF\s bylaws/etc. As I understand it, the board has delegated responsibility for the incubator, and thus incubator podlings, to the Incubator PMC and its members. Thus, it is only members of the Incubator PMC that have the ability to vote. This much is straight-forward. So, the question is, what options does the Incubator PMC have in terms of further delegating responsibility? Can the Incubator PMC delegate (some) responsibility to people who are not themselves incubator PMC members? To do so, does the Incubator PMC need to inform the board of the change of composition of 'sub-committees'? My thought is that if we can clarify what is legally possible, we will be better placed to find the appropriate model for the incubator that fits within those legal/bylaw bounds. I was wondering the same. This seems to enable such: RESOLVED, that the initial Apache Incubator PMC be and hereby is tasked with the creation of a set of bylaws intended to encourage open development and increased participation in the Apache Incubator Project. http://incubator.apache.org/official/resolution.html Oooh, i overlooked the word initial. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Please add my account to the ContributorsGroup
James Taylor wrote: Hello, Please add my account, James.Taylor to the ContributorsGroup as I'd like to create a wiki for a new proposal for an Apache Incubator project. Done. Thanks, James https://wiki.apache.org/incubator/ContributorsGroup - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Wiki access
P. Taylor Goetz wrote: I'm requesting access to the incubator wiki in order to update the storm podling monthly board report. As explained at the front page top-right, you need to tell us your Wiki username. http://wiki.apache.org/incubator/ -David Thanks in advance. P. Taylor Goetz Software Architect Health Market Science The Science of Better Results 2700 Horizon Drive •King of Prussia, PA • 19406 P: 610.994.5237 • M: 610.212.1185 •healthmarketscience.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Wiki access
P. Taylor Goetz wrote: P. Taylor Goetz Thanks and my apologies for being a little thick regarding the right process. I'm kind of juggling eggs right now... Okay, done now. I did not realise that spaces were allowed. -David P. Taylor Goetz Software Architect Health Market Science The Science of Better Results 2700 Horizon Drive •King of Prussia, PA • 19406 P: 610.994.5237 • M: 610.212.1185 •healthmarketscience.com On Nov 5, 2013, at 8:01 PM, sebb seb...@gmail.com wrote: What is your Wiki login name? On 6 November 2013 00:55, P. Taylor Goetz ptgo...@gmail.com wrote: I'm requesting access to the incubator wiki in order to update the storm podling monthly board report. Thanks in advance. P. Taylor Goetz Software Architect Health Market Science The Science of Better Results 2700 Horizon Drive •King of Prussia, PA • 19406 P: 610.994.5237 • M: 610.212.1185 •healthmarketscience.com - 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: please follow through to publish doc changes
David Crossley wrote: The problem seems to be getting worse. Some people make source changes to docs, but then do not follow through to publish those changes via the CMS. Then other changes bank up behind the logjam. http://incubator.apache.org/guides/website.html This continues to be a problem. It is now exacerbated because someone has made source content errors (knox) but because people do not bother to try to publish changes, these errors are not noticed or attended to. It is preventing other people from working. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: the Voting Status monitor is overloaded
David Crossley wrote: It seems that the brilliant Voting Status monitor has fallen into disrepair. Partly due to people not properly following up with a clear RESULT tally and partly perhaps inadequacies of the monitor script. Follow the top-left link from the Incubator home: http://incubator.apache.org/ Items coloured any shade of orange need attention. We all need to care for these tools to assist us through incubation efficiently. Would people who have an interest in each open entry please review the email archives to see why your result summary tally email was not detected. Perhaps you forgot to prepend [RESULT]. Or maybe changed the email Subject too and so confused the monitor. If so then please send a followup to your VOTE thread. That will cause the monitor to clear its backlog. However, i do see some that should be marked as Resolved. So maybe the script that does this scan needs tweaks to pattern matching. The code is there for all in the top-level of Incubator SVN. http://incubator.apache.org/facilities.html#voting-status Please add more instructions to the docs: http://incubator.apache.org/facilities.html#voting-status I am dismayed. Only one person bothered to follow up. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
the Voting Status monitor is overloaded
It seems that the brilliant Voting Status monitor has fallen into disrepair. Partly due to people not properly following up with a clear RESULT tally and partly perhaps inadequacies of the monitor script. Follow the top-left link from the Incubator home: http://incubator.apache.org/ Items coloured any shade of orange need attention. We all need to care for these tools to assist us through incubation efficiently. Would people who have an interest in each open entry please review the email archives to see why your result summary tally email was not detected. Perhaps you forgot to prepend [RESULT]. Or maybe changed the email Subject too and so confused the monitor. If so then please send a followup to your VOTE thread. That will cause the monitor to clear its backlog. However, i do see some that should be marked as Resolved. So maybe the script that does this scan needs tweaks to pattern matching. The code is there for all in the top-level of Incubator SVN. http://incubator.apache.org/facilities.html#voting-status Please add more instructions to the docs: http://incubator.apache.org/facilities.html#voting-status -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Graduated projects need to clean up (Was: svn commit: r1532364)
Please do not hand-edit the generated files. Graduating projects need to follow a number of steps. The docs do explain those steps. Clutch tries to help by linking to some relevant docs. See the notes against the DeltaSpike entry and other graduated projects: http://incubator.apache.org/clutch.html#other Please encourage projects to clean up after themselves. There are more clean-up steps than just editing a text file. -David j...@apache.org wrote: Author: jim Date: Tue Oct 15 14:36:36 2013 New Revision: 1532364 URL: http://svn.apache.org/r1532364 Log: graduated Modified: incubator/public/trunk/content/clutch.txt Modified: incubator/public/trunk/content/clutch.txt URL: http://svn.apache.org/viewvc/incubator/public/trunk/content/clutch.txt?rev=1532364r1=1532363r2=1532364view=diff == --- incubator/public/trunk/content/clutch.txt (original) +++ incubator/public/trunk/content/clutch.txt Tue Oct 15 14:36:36 2013 @@ -7,7 +7,6 @@ blur,Blur,Incubator celix,Celix,Incubator chukwa,Chukwa,Incubator curator,Curator,Incubator -deltaspike,DeltaSpike,Incubator devicemap,DeviceMap,Incubator drill,Drill,Incubator droids,Droids,HttpComponents, Lucene - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[RESULT][VOTE] Usergrid BaaS Stack for Apache Incubator (revised proposal)
Adjusting the email Subject to [RESULT][VOTE] ... to enable the voting status monitor: http://incubator.apache.org/facilities.html#voting-status -David Dave wrote: I am officially closing the vote. We have 11 binding +1 votes, 4 non-binding votes and no -1 notes. Usergrid is now officially part of the Apache Incubator. Thanks to everybody who helped put together the proposal, those who joined the discussion, those who voted and the Usergrid community. +1 binding votes Afkham Azeez Alan D. Cabrera Alex Karasulu Ate Douma Bertrand Delacretaz Chip Childers David Nalley Henry Saputra Jim Jagielski Luciano Resende Marvin Humphrey +1 non-binding Larry McCay Lewis John Mcgibbney Lieven Govaerts Raminder Singh Totals 11 binding +1 votes 4 non-binding +1 votes 0 -1 votes Thanks, Dave PS. this also happens to be the 2nd anniversary of the day that Usergrid was released on Github. Happy Birthday Usergrid! - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Apache project bylaws
Martijn Dashorst wrote: On Tue, Oct 1, 2013 at 5:28 PM, Ross Gardler rgard...@opendirective.com wrote: +1 to Marvin's I hope that most projects won't bother although there needs to be something a little more than a blank piece of paper. The best approach, IMHO, is to simply make it official that the project adopts the same byelaws as project x, y or z. Pick an established project that has a minimal set of stable byelaws and go on from there. Some projects like to refer to the original project pages, others make a local copy. Both approaches have their advantages. At Wicket we didn't bother to pick bylaws and from what I have seen in other communities we are better for it. Graduation from the incubator is a testament that the community acts as a meritocracy, and the bylaws of the foundation should be good for all graduated projects. As a community I think that Wicket developers never even bothered to look at the bylaws and just follow the established processes and guidances that trickle down from board@. Looking at httpd, they don't have explicit bylaws either–my google fu did not unearth any document at httpd.apache.org that constitutes bylaws. Many project call them guidelines. http://httpd.apache.org/dev/guidelines.html -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Apache project bylaws
Justin Mclean wrote: Hi, Looks like one of the things that fell between the cracks when Apache Flex become a top level project was drafting up and accepting a set of bylaws. I see nothing about bylaws on the incubator website, including here [1] where I would expect it to be. Should the process on this page be updated? Are bylaws optional or should they be a required part of graduation? I reckon that this is one of the initial steps of becoming a top-level project (TLP). See the board resolution that created your TLP: hereby is tasked with the creation of a set of bylaws to ... Review/adopt/adapt the bylaws of other projects that have gone before you. I reckon that it is beyond the Incubator. Yes the docs should mention that future task. -David Thanks, Justin 1. http://incubator.apache.org/guides/graduation.html PS We're in the process of putting our bylaws together here. Still in very early draft form, suggestions and/or advice is welcome. https://cwiki.apache.org/confluence/display/FLEX/Draft+Bylaws - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT] [VOTE] Accept Storm into the Incubator
Doug Cutting wrote: On Thu, Sep 12, 2013 at 12:19 PM, Doug Cutting cutt...@apache.org wrote: I'd like to call a vote to accept Storm as a new Incubator podling. This passes, with lots of +1 votes (plenty by PMC members) and no -1 votes. Thanks for voting. Doug Someone from the Storm project needs to follow the initial steps: http://incubator.apache.org/clutch.html#h-Project http://incubator.apache.org/guides/mentor.html#Overview -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [RESULT] [VOTE] Accept Storm into the Incubator
David Crossley wrote: Doug Cutting wrote: On Thu, Sep 12, 2013 at 12:19 PM, Doug Cutting cutt...@apache.org wrote: I'd like to call a vote to accept Storm as a new Incubator podling. This passes, with lots of +1 votes (plenty by PMC members) and no -1 votes. Thanks for voting. Doug Someone from the Storm project needs to follow the initial steps: http://incubator.apache.org/clutch.html#h-Project http://incubator.apache.org/guides/mentor.html#Overview Argh, do not panic :-) I see now that it is listed. Must have been looking at a stale page. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: perms on wiki
Romain Manni-Bucau wrote: Hi, anyone can give me permissions to edit the wiki please? (i would like to create a proposal) Yes, but you do need to provide the crucial information: your wiki username. See the top-right of http://wiki.apache.org/incubator/ -David Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Write access to wiki
Nathan Marz wrote: May I have write access to the incubator wiki (username NathanMarz) so that I can add a proposal for Storm? Thanks, Nathan Done. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
svn configuration for all committers
See: http://apache.org/dev/version-control.html#https-svn-config -David sebb wrote: On 18 August 2013 16:27, dasho...@apache.org wrote: Author: dashorst Date: Sun Aug 18 15:27:12 2013 New Revision: 1515136 URL: http://svn.apache.org/r1515136 Log: Added IP clearance for Wicket Guide snip/ Added: incubator/public/trunk/content/ip-clearance/wicket-andrea-del-bene-wicket-guide.xml URL: http://svn.apache.org/viewvc/incubator/public/trunk/content/ip-clearance/wicket-andrea-del-bene-wicket-guide.xml?rev=1515136view=auto == Binary file - no diff available. Propchange: incubator/public/trunk/content/ip-clearance/wicket-andrea-del-bene-wicket-guide.xml -- svn:mime-type = application/xml Please don't use application/xml - it causes SVN to treat the files as binary. Use text/xml instead (or don't use a mime-type) I've fixed the file so future changes will be visible - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Canonical podling count
Marvin Humphrey wrote: Tim Williams william...@gmail.com wrote: Why not take it from the number Clutch reports? Ah, here, just above the table: http://incubator.apache.org/clutch.html#current Also see http://incubator.apache.org/clutch.html#data which shows the clutch.txt list of current podlings. There is also the Incubator History chart: http://incubator.apache.org/history/ (However it has stopped working for me recently.) See the links from: http://incubator.apache.org/facilities.html -David Also in svn. http://svn.apache.org/repos/asf/incubator/public/trunk/content/clutcht.ent Thanks, Tim. (PS: the algo in my previous mail counts dupes, so no one should ever use it.) Marvin Humphrey - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: svn commit: r1496076 - /incubator/public/trunk/content/projects/stratos.xml
Please fix this. It breaks the build of the Incubator website. The xml error is: [anakia] Error: The string -- is not permitted within comments. [anakia]Line: 12 Column: 8 -David az...@apache.org wrote: Author: azeez Date: Mon Jun 24 15:02:55 2013 New Revision: 1496076 URL: http://svn.apache.org/r1496076 Log: Updated Modified: incubator/public/trunk/content/projects/stratos.xml Modified: incubator/public/trunk/content/projects/stratos.xml URL: http://svn.apache.org/viewvc/incubator/public/trunk/content/projects/stratos.xml?rev=1496076r1=1496075r2=1496076view=diff == --- incubator/public/trunk/content/projects/stratos.xml [utf-8] (original) +++ incubator/public/trunk/content/projects/stratos.xml [utf-8] Mon Jun 24 15:02:55 2013 @@ -2,11 +2,12 @@ document properties -titleIncubation Status Template/title +titleStratos Project Incubation Status/title link href=http://purl.org/DC/elements/1.0/; rel=schema.DC/ /properties body +!-- pre-8-lt; cut here ---8-lt; cut here ---8-lt; cut here ---8-lt;/pre section id=Project+Incubation+Status+TEMPLATE @@ -36,23 +37,24 @@ /p /section pre-8-lt; cut here ---8-lt; cut here ---8-lt; cut here ---8-lt;/pre +-- - -section id=XYZ+Project+Incubation+Status - titleXYZ Project Incubation Status/title +section id=Stratos+Project+Incubation+Status + titleStratos Project Incubation Status/title pThis page tracks the project status, incubator-wise. For more general project status, look on the project website./p /section section id=Description titleDescription/title - pThe XYZ Project is a wonderful project that does things and goes places./p + pStratos is a polyglot PaaS framework, providing developers a cloud-based environment for developing, testing, and running scalable applications, and IT providers high utilization rates, automated resource management, and platform-wide insight including monitoring and billing./p /section + section id=News titleNews/title ul !--li-MM-DD New committer: Fred Nerk/li-- -li-MM-DD Project enters incubation./li +li2013-06-20 Project enters incubation./li /ul /section section id=Project+info @@ -80,7 +82,7 @@ tdWebsite/td tdwww/td td id=www -a href=http://incubator.apache.org/XYZ/;http://incubator.apache.org/XYZ//a +a href=http://incubator.apache.org/stratos/;http://incubator.apache.org/stratos//a /td /tr tr @@ -91,43 +93,136 @@ tr tdMailing list/td tddev/td - td id=mail-devcodePROJECT-dev/codecode@/codecodeincubator.apache.org/code/td + td id=mail-devcodedev/codecode@/codecodestratos.incubator.apache.org/code/td /tr tr td./td tdcommits/td - td id=mail-commitscodePROJECT-commits/codecode@/codecodeincubator.apache.org/code/td + td id=mail-commitscodecommits/codecode@/codecodestratos.incubator.apache.org/code/td /tr tr tdBug tracking/td td./td td id=tracker -[ provide expected link ] +a href=https://issues.apache.org/jira/browse/STRATOS;https://issues.apache.org/jira/browse/STRATOS/a /td /tr tr tdSource code/td - tdSVN/td - td id=svn -a href=https://svn.apache.org/repos/asf/incubator/XYZ/;https://svn.apache.org/repos/asf/incubator/XYZ//a + tdGit/td + td id=git +a href=https://git-wip-us.apache.org/repos/asf/incubator-stratos.git;https://git-wip-us.apache.org/repos/asf/incubator-stratos.git/a /td /tr tr tdMentors/td - tdid1/td - tdName1 Surname1/td + tdazeez/td + tdAfkham Azeez/td +/tr +tr + td./td + tdsmarru/td + tdSuresh Marru/td +/tr +tr + td./td + tdmpierce/td + tdMarlon Pierce/td /tr tr td./td - tdid2/td - tdName2 Surname2/td + tdchipchilders/td + tdChip Childers/td +/tr +tr + td./td + tdmnour/td + tdMohammad Nour/td +/tr +tr + td./td + tdnslater/td + tdNoah Slater/td +/tr +tr + td./td + tdantelder/td + tdAnt Elder/td /tr tr tdCommitters/td + tdpzf/td + tdPaul Fremantle/td
Re: svn commit: r1496076 - /incubator/public/trunk/content/projects/stratos.xml
David Crossley wrote: Please fix this. It breaks the build of the Incubator website. The xml error is: [anakia] Error: The string -- is not permitted within comments. [anakia]Line: 12 Column: 8 As explained at the top of the template file from which this was copied, need to remove the various explanatory sections. Just commenting-out the comments does break the xml. As well as those instructions, here is one route to find other various assistance with that task: http://incubator.apache.org/clutch.html#h-hasStatusEntry http://incubator.apache.org/guides/ppmc.html#Project+Status+Updates http://incubator.apache.org/guides/website.html#Edit+your+project+status+page -David az...@apache.org wrote: Author: azeez Date: Mon Jun 24 15:02:55 2013 New Revision: 1496076 URL: http://svn.apache.org/r1496076 Log: Updated Modified: incubator/public/trunk/content/projects/stratos.xml Modified: incubator/public/trunk/content/projects/stratos.xml URL: http://svn.apache.org/viewvc/incubator/public/trunk/content/projects/stratos.xml?rev=1496076r1=1496075r2=1496076view=diff == --- incubator/public/trunk/content/projects/stratos.xml [utf-8] (original) +++ incubator/public/trunk/content/projects/stratos.xml [utf-8] Mon Jun 24 15:02:55 2013 @@ -2,11 +2,12 @@ document properties -titleIncubation Status Template/title +titleStratos Project Incubation Status/title link href=http://purl.org/DC/elements/1.0/; rel=schema.DC/ /properties body +!-- pre-8-lt; cut here ---8-lt; cut here ---8-lt; cut here ---8-lt;/pre section id=Project+Incubation+Status+TEMPLATE @@ -36,23 +37,24 @@ /p /section pre-8-lt; cut here ---8-lt; cut here ---8-lt; cut here ---8-lt;/pre +-- - -section id=XYZ+Project+Incubation+Status - titleXYZ Project Incubation Status/title +section id=Stratos+Project+Incubation+Status + titleStratos Project Incubation Status/title pThis page tracks the project status, incubator-wise. For more general project status, look on the project website./p /section section id=Description titleDescription/title - pThe XYZ Project is a wonderful project that does things and goes places./p + pStratos is a polyglot PaaS framework, providing developers a cloud-based environment for developing, testing, and running scalable applications, and IT providers high utilization rates, automated resource management, and platform-wide insight including monitoring and billing./p /section + section id=News titleNews/title ul !--li-MM-DD New committer: Fred Nerk/li-- -li-MM-DD Project enters incubation./li +li2013-06-20 Project enters incubation./li /ul /section section id=Project+info @@ -80,7 +82,7 @@ tdWebsite/td tdwww/td td id=www -a href=http://incubator.apache.org/XYZ/;http://incubator.apache.org/XYZ//a +a href=http://incubator.apache.org/stratos/;http://incubator.apache.org/stratos//a /td /tr tr @@ -91,43 +93,136 @@ tr tdMailing list/td tddev/td - td id=mail-devcodePROJECT-dev/codecode@/codecodeincubator.apache.org/code/td + td id=mail-devcodedev/codecode@/codecodestratos.incubator.apache.org/code/td /tr tr td./td tdcommits/td - td id=mail-commitscodePROJECT-commits/codecode@/codecodeincubator.apache.org/code/td + td id=mail-commitscodecommits/codecode@/codecodestratos.incubator.apache.org/code/td /tr tr tdBug tracking/td td./td td id=tracker -[ provide expected link ] +a href=https://issues.apache.org/jira/browse/STRATOS;https://issues.apache.org/jira/browse/STRATOS/a /td /tr tr tdSource code/td - tdSVN/td - td id=svn -a href=https://svn.apache.org/repos/asf/incubator/XYZ/;https://svn.apache.org/repos/asf/incubator/XYZ//a + tdGit/td + td id=git +a href=https://git-wip-us.apache.org/repos/asf/incubator-stratos.git;https://git-wip-us.apache.org/repos/asf/incubator-stratos.git/a /td /tr tr tdMentors/td - tdid1/td - tdName1 Surname1/td + tdazeez/td + tdAfkham Azeez/td +/tr +tr + td./td + tdsmarru/td + tdSuresh Marru/td +/tr +tr
Re: [MENTOR] Re: Missing Release Distribution in Clutch Status?
Mattmann, Chris A (398J) wrote: Hey Guys, Sorry I missed this. Real quick CC to general@i.a.o. I'm not an expert in the Clutch. IPMC peeps that know the clutch, Knox has a release in the dist area: http://www.apache.org/dyn/closer.cgi/incubator/knox/ (^^ for example the 0.2.0 release) Can someone give us some insight as to why the clutch indicates we don't have a release in the distro area? See the Knox entry in the Other issues section: http://incubator.apache.org/clutch.html#other It is because Knox is missing the required file naming convention: http://incubator.apache.org/clutch.html#h-hasRelease So the cron job that scans for releases does not find it. -David Thank you! Cheers, Chris ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: larry mccay larry.mc...@gmail.com Reply-To: d...@knox.incubator.apache.org d...@knox.incubator.apache.org Date: Thursday, June 20, 2013 11:46 AM To: d...@knox.incubator.apache.org d...@knox.incubator.apache.org Subject: [MENTOR] Re: Missing Release Distribution in Clutch Status? adding mentor prefix... On Mon, Jun 17, 2013 at 3:40 PM, larry mccay larry.mc...@gmail.com wrote: Touching this to bring it back to the top... @Chris - do you have any insight into this status indicator for us? On Thu, Jun 13, 2013 at 2:51 PM, larry mccay larry.mc...@gmail.comwrote: Here is the location of ambari - who has a true for release bits column - of course this is just one mirror - not sure how to map the mirrors: http://www.us.apache.org/dist/incubator/ambari/ambari-0.9-incubating/ relative path seems to map correctly to me... On Thu, Jun 13, 2013 at 2:32 PM, Kevin Minder kevin.min...@hortonworks.com wrote: We do have release bits in http://www.apache.org/dist/**incubator/knox/0.2.0/http://www.apache.or g/dist/incubator/knox/0.2.0/ I wonder if they need to be in the root? On 6/13/13 1:29 PM, larry mccay wrote: All - This page shows the status of clutch currently in incubation. It indicates that we don't have a release in our distribution area. Does this mean that we don't have our release in the right place? http://incubator.apache.org/**clutch.htmlhttp://incubator.apache.org/ clutch.html thanks, --larry - 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
please follow through to publish doc changes
The problem seems to be getting worse. Some people make source changes to docs, but then do not follow through to publish those changes via the CMS. Then other changes bank up behind the logjam. http://incubator.apache.org/guides/website.html -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: please follow through to publish doc changes
Mattmann, Chris A (398J) wrote: Hi David, That's my bad. Having not published the site using the CMS since we switched over, I knew I had to read the docs again but hadn't. I fully intended to though. Not only you. It is a common holdup. There are various routes for editing, as explained at [1]. I take the quick way. With an SVN checkout, i edit the source and commit, then wait a little, then https://cms.apache.org/incubator/publish look at the diff (reload if necessary until CMS catches up) then publish. I only build locally (via e.g. './build.sh') if i am doing major edits/additions, or if the CMS is wedged which usually means that someone has an xml error with their source edits. The [1] does need some clarifications in that regard. [1] http://incubator.apache.org/guides/website.html Anyway, i did just now publish the backlog. -David Anyways, sorry. Cheers, Chris ++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattm...@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++ -Original Message- From: David Crossley cross...@apache.org Reply-To: general@incubator.apache.org general@incubator.apache.org Date: Thursday, June 20, 2013 7:11 PM To: general@incubator.apache.org general@incubator.apache.org Subject: please follow through to publish doc changes The problem seems to be getting worse. Some people make source changes to docs, but then do not follow through to publish those changes via the CMS. Then other changes bank up behind the logjam. http://incubator.apache.org/guides/website.html -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Accept Stratos proposal as an incubating project
Good on you. Keep it up. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: A lot of reports missing these period
David Crossley wrote: Marvin sends a summary to IPMC private@ list. It did include both MRQL and Ambari. They are listed in this summary (generated from content/podlings.xml): http://incubator.apache.org/report-groups.txt and in this month's data list: http://incubator.apache.org/report_due_2.txt I looked at each mailing list archive of those due to report. The reminder was delivered to all projects except: jclouds : the mailing list was not ready at that time ambari, mrql, tajo For the latter three, was the message stuck in your email moderation queue? Also remember that it is clear when your project is due to report. See the above references. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: A lot of reports missing these period
Marvin sends a summary to IPMC private@ list. It did include both MRQL and Ambari. They are listed in this summary (generated from content/podlings.xml): http://incubator.apache.org/report-groups.txt and in this month's data list: http://incubator.apache.org/report_due_2.txt -David Benson Margulies wrote: We should make sure the front of the report indicates the Marvin Mishap. On Thu, May 9, 2013 at 5:29 PM, Mahadev Konar maha...@hortonworks.com wrote: Similar with Ambari. I dont think we saw a Marvin notice for May. Should we send out a report the next months Board Report? thanks mahadev On Tue, May 7, 2013 at 2:04 PM, Alan Cabrera l...@toolazydogs.com wrote: How odd. I don't think that MRQL received the notice from Marvin. Regards, Alan On May 7, 2013, at 1:42 PM, Christian Grobmeier grobme...@gmail.com wrote: Folks, its reporting time and at the wiki are a lot of them missing! http://wiki.apache.org/incubator/May2013 Ambari Blur DeltaSpike (hasn't it graduated?) Droids Falcon Hadoop Development Tools MRQL Open Climate Workbench Provisionr Tajo Tez Please mentors of these projects catch up with your podlings. Cheers Christian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: A lot of reports missing these period
Mahadev Konar wrote: David, Doesnt it send an email to the dev mailing list? Yes it does send to each podling's dev list. Please see the data list referenced below. The additional summary that goes to the IPMC private list shows the set of delivery addresses, which does include those that Marvin is being blamed for. -David David Crossley wrote: Marvin sends a summary to IPMC private@ list. It did include both MRQL and Ambari. They are listed in this summary (generated from content/podlings.xml): http://incubator.apache.org/report-groups.txt and in this month's data list: http://incubator.apache.org/report_due_2.txt -David Benson Margulies wrote: We should make sure the front of the report indicates the Marvin Mishap. On Thu, May 9, 2013 at 5:29 PM, Mahadev Konar maha...@hortonworks.com wrote: Similar with Ambari. I dont think we saw a Marvin notice for May. Should we send out a report the next months Board Report? thanks mahadev On Tue, May 7, 2013 at 2:04 PM, Alan Cabrera l...@toolazydogs.com wrote: How odd. I don't think that MRQL received the notice from Marvin. Regards, Alan On May 7, 2013, at 1:42 PM, Christian Grobmeier grobme...@gmail.com wrote: Folks, its reporting time and at the wiki are a lot of them missing! http://wiki.apache.org/incubator/May2013 Ambari Blur DeltaSpike (hasn't it graduated?) Droids Falcon Hadoop Development Tools MRQL Open Climate Workbench Provisionr Tajo Tez Please mentors of these projects catch up with your podlings. Cheers Christian - 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: marvin report reminders
Alan Cabrera wrote: David Crossley wrote: Alan Cabrera wrote: Does anyone know where the Marvin code bits live? At https://svn.apache.org/repos/infra/infrastructure/trunk/tools/board_reminders/ There are various discussions in the Incubator archives about how the data lists (for mail addresses for each project due to report each month) are currently generated. Now that mail list names are more consistent for newer podlings, some of that process could be handled outside of Clutch. So the process is by naming convention rather than explicit declarations? For the old stuck projects, Clutch gathers various hints about their dev mail list addresses. For the recently entered podlings, i gather that it is always dev@podling. Clutch also makes sure that each list is operational, otherwise it uses the general@ list for that podling (which unfortunately misses the project's name). Sorry, no time now. This local search gave plenty of hits on previous and more detailed explanations of the process: mairix a:incubator,general f:crossley report,generated,clutch -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
marvin report reminders
Alan Cabrera wrote: Does anyone know where the Marvin code bits live? At https://svn.apache.org/repos/infra/infrastructure/trunk/tools/board_reminders/ There are various discussions in the Incubator archives about how the data lists (for mail addresses for each project due to report each month) are currently generated. Now that mail list names are more consistent for newer podlings, some of that process could be handled outside of Clutch. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: A lot of reports missing these period
Christian Grobmeier wrote: Folks, its reporting time and at the wiki are a lot of them missing! http://wiki.apache.org/incubator/May2013 Ambari Blur DeltaSpike (hasn't it graduated?) The Voting Status page indicates that they have not finalised their graduation vote, nor commenced the graduation steps. So the incubator records and automated systems are wonky. -David Droids Falcon Hadoop Development Tools MRQL Open Climate Workbench Provisionr Tajo Tez Please mentors of these projects catch up with your podlings. Cheers Christian - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
configuration of svn [Was: svn commit: r1477438 - /incubator/public/trunk/content/projects/jclouds.xml]
How do new files that are added to svn, get these properties set? We cannot see the diffs. There are also other new ones in SVN that do not have eol-style set. http://apache.org/dev/version-control.html#https-svn-config Is it that people do not have correct configuration, or is this the CMS? -David sma...@apache.org wrote: Author: smarru Date: Tue Apr 30 01:17:52 2013 New Revision: 1477438 URL: http://svn.apache.org/r1477438 Log: adding jclouds template status page Added: incubator/public/trunk/content/projects/jclouds.xml (with props) Added: incubator/public/trunk/content/projects/jclouds.xml URL: http://svn.apache.org/viewvc/incubator/public/trunk/content/projects/jclouds.xml?rev=1477438view=auto == Binary file - no diff available. Propchange: incubator/public/trunk/content/projects/jclouds.xml -- svn:mime-type = application/xml - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: configuration of svn [Was: svn commit: r1477438 - /incubator/public/trunk/content/projects/jclouds.xml]
Thanks for the additional information. Would the following people please attend to their configuration: http://apache.org/dev/version-control.html#https-svn-config These are the initial committers for the following recently added files: phunt : content/projects/curator.xml acmurthy : content/projects/falcon.xml rvs : content/projects/hdt.xml marru : content/projects/jclouds.xml ddas : content/projects/knox.xml edwardyoon : content/projects/mrql.xml mfranklin : content/projects/streams.xml jghoman : content/projects/tajo.xml acmurthy : content/projects/tez.xml There are also a stack of recent ones under content/ip-clearance/ directory. Would people who have recently added files there please fix yourself. -David sebb wrote: A further wrinkle here is that SVN treats application/xml as binary. To be treated as text, an XML file needs to be text/xml or similar, see: http://subversion.apache.org/faq.html#binary-files On 6 May 2013 10:25, Greg Stein gst...@gmail.com wrote: After you add a file (and before commit), you can use 'svn propset' to set properties. In addition, there are auto props in your personal configuration file. If people in a group don't have the autoprops set similarly, then your default props can (obviously) vary. Subversion 1.8 (*) will provide assistance with unifying autoprops across group members. Cheers, -g [1] http://subversion.apache.org/docs/release-notes/1.8.html#repos-dictated-config On Mon, May 6, 2013 at 4:18 AM, David Crossley cross...@apache.org wrote: How do new files that are added to svn, get these properties set? We cannot see the diffs. There are also other new ones in SVN that do not have eol-style set. http://apache.org/dev/version-control.html#https-svn-config Is it that people do not have correct configuration, or is this the CMS? -David sma...@apache.org wrote: Author: smarru Date: Tue Apr 30 01:17:52 2013 New Revision: 1477438 URL: http://svn.apache.org/r1477438 Log: adding jclouds template status page Added: incubator/public/trunk/content/projects/jclouds.xml (with props) Added: incubator/public/trunk/content/projects/jclouds.xml URL: http://svn.apache.org/viewvc/incubator/public/trunk/content/projects/jclouds.xml?rev=1477438view=auto == Binary file - no diff available. Propchange: incubator/public/trunk/content/projects/jclouds.xml -- svn:mime-type = application/xml - 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: improve podling management and status information
David Crossley wrote: There is still some duplication of information for the status of each podling between the main file [1] and each podling status web page. We also need each podling to take more care of their status metadata. One aspect is the Sponsor/Champion/Mentors information. To reduce this duplication and out-of-date-ness, each podling status page could simply link to the central information, rather than repeat that in their status page. e.g. http://incubator.apache.org/projects/#allura http://incubator.apache.org/projects/#devicemap That page is automatically generated whenever someone edits the metadata summary file [1]. (Which then need to be committed too.) There is also a very important past discussion that did already address many other aspects of the management of the projects. We still need to implement that. Here is one thread. Go deeper into that thread where there is discussion about fixing various aspects. Subject: incubator is a single group Date: 2011-11-11 07:58:50 GMT http://s.apache.org/Ow0 [1] https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
improve podling management and status information
There is still some duplication of information for the status of each podling between the main file [1] and each podling status web page. We also need each podling to take more care of their status metadata. One aspect is the Sponsor/Champion/Mentors information. To reduce this duplication and out-of-date-ness, each podling status page could simply link to the central information, rather than repeat that in their status page. e.g. http://incubator.apache.org/projects/#allura http://incubator.apache.org/projects/#devicemap That page is automatically generated whenever someone edits the metadata summary file [1]. (Which then need to be committed too.) There is also a very important past discussion that did already address many other aspects of the management of the projects. We still need to implement that. [1] https://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: fix entry and exit documentation etc.
David Crossley wrote: Daniel Shahaf wrote: Reviewing this, the document you added a link to contains bugs. Yes, there are many issues with Incubator documentation. Thanks for detecting some of them. Procedures have been changed, so documentation needs to catch up. Every committer has access to these documents. I will continue to fix things bit-by-bit and still encourage people who have been through the process to help fix this documentation to make the path better for those who follow. At the moment i do not have time, and i am expecting others to do this. No-one did. So i have made time to do some. Would someone else please do the rest. -David See also the following message regarding r1465544. -David Specifically, http://incubator.apache.org/guides/mentor.html#Set+Up+Repository is wrong (it contradicts http://www.apache.org/dev/infra-contact#requesting-podling) and http://incubator.apache.org/guides/mentor.html#request-mailing-lists is bitrotted (list addresses in the example are wrong). I didn't check whether there are other bugs besides these two. -- Not subscribed cross...@apache.org wrote on Mon, Apr 08, 2013 at 06:51:26 -: Author: crossley Date: Mon Apr 8 06:51:26 2013 New Revision: 1465541 URL: http://svn.apache.org/r1465541 Log: Link to explanation of first steps for new podlings and the metadata summary file. Modified: infrastructure/site/trunk/content/dev/infra-contact.mdtext Modified: infrastructure/site/trunk/content/dev/infra-contact.mdtext URL: http://svn.apache.org/viewvc/infrastructure/site/trunk/content/dev/infra-contact.mdtext?rev=1465541r1=1465540r2=1465541view=diff == --- infrastructure/site/trunk/content/dev/infra-contact.mdtext (original) +++ infrastructure/site/trunk/content/dev/infra-contact.mdtext Mon Apr 8 06:51:26 2013 @@ -85,7 +85,8 @@ The podling creation process is as follo 1. The IPMC vote passes. -1. The podling is added to the IPMC's `podlings.xml` file with `status=current`. +1. The podling is added to the IPMC's `podlings.xml` summary file with `status=current`. +(See [notes][6] about that, and other initial tasks.) 1. An ASF Member or PMC chair files [mailing list creation requests][2]. @@ -257,3 +258,4 @@ Reminder: this facility is for emergency [3]: https://infra.apache.org/officers/webreq [4]: http://people.apache.org/committers-by-project.html#infrastructure-root [5]: https://svn.apache.org/repos/private/committers/board/committee-info.txt +[6]: http://incubator.apache.org/guides/mentor.html#Overview - 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
fix entry and exit documentation etc.
Daniel Shahaf wrote: Reviewing this, the document you added a link to contains bugs. Yes, there are many issues with Incubator documentation. Thanks for detecting some of them. Procedures have been changed, so documentation needs to catch up. Every committer has access to these documents. I will continue to fix things bit-by-bit and still encourage people who have been through the process to help fix this documentation to make the path better for those who follow. At the moment i do not have time, and i am expecting others to do this. See also the following message regarding r1465544. -David Specifically, http://incubator.apache.org/guides/mentor.html#Set+Up+Repository is wrong (it contradicts http://www.apache.org/dev/infra-contact#requesting-podling) and http://incubator.apache.org/guides/mentor.html#request-mailing-lists is bitrotted (list addresses in the example are wrong). I didn't check whether there are other bugs besides these two. -- Not subscribed cross...@apache.org wrote on Mon, Apr 08, 2013 at 06:51:26 -: Author: crossley Date: Mon Apr 8 06:51:26 2013 New Revision: 1465541 URL: http://svn.apache.org/r1465541 Log: Link to explanation of first steps for new podlings and the metadata summary file. Modified: infrastructure/site/trunk/content/dev/infra-contact.mdtext Modified: infrastructure/site/trunk/content/dev/infra-contact.mdtext URL: http://svn.apache.org/viewvc/infrastructure/site/trunk/content/dev/infra-contact.mdtext?rev=1465541r1=1465540r2=1465541view=diff == --- infrastructure/site/trunk/content/dev/infra-contact.mdtext (original) +++ infrastructure/site/trunk/content/dev/infra-contact.mdtext Mon Apr 8 06:51:26 2013 @@ -85,7 +85,8 @@ The podling creation process is as follo 1. The IPMC vote passes. -1. The podling is added to the IPMC's `podlings.xml` file with `status=current`. +1. The podling is added to the IPMC's `podlings.xml` summary file with `status=current`. +(See [notes][6] about that, and other initial tasks.) 1. An ASF Member or PMC chair files [mailing list creation requests][2]. @@ -257,3 +258,4 @@ Reminder: this facility is for emergency [3]: https://infra.apache.org/officers/webreq [4]: http://people.apache.org/committers-by-project.html#infrastructure-root [5]: https://svn.apache.org/repos/private/committers/board/committee-info.txt +[6]: http://incubator.apache.org/guides/mentor.html#Overview - 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: Proposal for better docs on trademark research (Incubator)
Daniel Shahaf wrote: Christian Grobmeier wrote: Daniel Shahaf wrote: +liGitHub/li +liSourceForge.net/li +liGoogle Code/li +liOhloh/li +lia href=http://tsdr.uspto.gov;USPTO/a/li +liGoogle, Bing, Yahoo/li +lia href=http://www.trademarkia.com;Trademarkia/a/li Errr. Isn't this list of resources already available on another page? If so please just point to it, rather than duplicate it. (There should be exactly one canonical location for such info.) I didn't find one, /me surprised Yes there was already documentation. See http://incubator.apache.org/guides/names.html Some of the discussions that devised the process: http://s.apache.org/suitable-names-search-1 Subject: Trademark Kill Searches... Date: 2011-10-25 http://s.apache.org/suitable-names-search-2 Subject: Suitable Names Search [WAS Re: Trademark Kill Searches...] Date: 2011-11-09 http://s.apache.org/suitable-names-search-3 Subject: [Podling Suitable Name Search] Feedback Please Date: 2011-11-22 http://s.apache.org/suitable-names-search-4 Subject: [POLL] Suitable Name Search: Drop Or Retain? Date: 2011-11-29 http://s.apache.org/suitable-names-search-5 Subject: Help Wanted: Improved Podling Name Search Documentation Date: 2012-01-15 http://s.apache.org/suitable-names-search-6 Subject: [names] Public Review Date: 2012-01-29 http://s.apache.org/suitable-names-search-7 Subject: Proposal for better docs on trademark research (Incubator) Date: 2013-03-18 -David thats why I took the time and worked on this docs. I extracted the information from the old Jira issues. Thanks. And BTW infra experience tells me info about execuding the PNS process (PODLINGNAMESEARCH) should live on www.a.o/foundation/marks/, but that might be an issue for another patch. Its PODLING name search. Because of this name I was looking in the incubator docs first. As long as it is not named NAMESEARCH only I think it belongs to the incubator. If you have a semantic argument (eg: why shouldn't Apache Steve have been expected to run a name search at some point) I'll be glad to hear it. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: all podlings please update and maintain project metadata
Christian Grobmeier wrote: Daniel Shahaf wrote: Shane Curcuru wrote: Separately, I'd love to hear any comments about how this kind of requirement is expressed in the graduation guides. I.e. is it clear, even to normal humans (i.e. 99.99% of the world who are not Incubator experts) that these things are required of TLPs before (and after) graduation? FWIW, https://www.apache.org/dev/infra-contact#requesting-graduation seems to be read and followed by most graduating projects. Ah, maybe we have identified the breakdown. Perhaps they skip the Incubator documentation. I reckon that we need to link in both directions. Guess we need to give this a little love: http://incubator.apache.org/guides/graduation.html#project-first-steps and point to the new docs (which are fantastic btw) Yes. We already do point to the infra docs. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: all podlings please update and maintain project metadata
Please maintain your incubation metadata. This then enables other volunteers to have information at their fingertips to assist them to assist others. There are also some automated processes that utilise this metadata, as also happens when you become a Top-Level Project (TLP). Please see previous email below. -David David Crossley wrote: Would all podlings please update and maintain your project metadata. It is up to your project members. This metadata is used by various processes to assist with managing the many projects in the Incubator. Please do not expect other people to do it for you. This will not scale, either now or when you are TLPs. Recently Clutch is detecting that there are many such issues [1]. The notes in that table try to assist by linking to some relevant documentation. Incoming projects need to add their details to content/podlings.xml Incubating projects need to keep that content up-to-date. Outgoing projects need to adjust that content as they go through the graduation phases. This then assists all volunteers to assist all volunteers. [1] http://incubator.apache.org/clutch.html#other -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Request for edit karma for incubator pages in http://wiki.apache.org/incubator
Henry Saputra wrote: Hi, I would like to ask for karma to edit proposal for incubator project. In particular http://wiki.apache.org/incubator/MetaModelProposal My wiki user name is Henry Saputrahttp://wiki.apache.org/incubator/Henry%20Saputra Done. However i am not sure how to deal with spaces in usernames. http://wiki.apache.org/incubator/ContributorsGroup -David Thank you, Henry - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Ripple, Streams, Onami, HDT need to fix your metadata
Ate Douma wrote: I've removed the monthly schedule for Streams too. Not sure how about updating the site though, can't find instruction how to trigger that, if even needed? After making source changes, then i just go to https://cms.apache.org/incubator/publish to publish the generated changes when they are ready. I did that now. The next time that someone runs Clutch (there are notes on that page) then it will pull together any pending metadata changes. -David On 03/05/2013 08:15 AM, David Crossley wrote: Ripple, Streams, Onami, Hadoop Development Tools ... Those projects would have received the email reminder about reporting. You need to care for your podling metadata in the content/podlings.xml file to take yourself off the monthly schedule and onto quarterly. (Unless you do want to keep doing monthly.) See column C and the help notes below the table: http://incubator.apache.org/clutch.html This file http://incubator.apache.org/report-groups.txt and http://incubator.apache.org/report_due_3.txt are generated from that content/podlings.xml file and are used to automate the reminders and other stuff. -David David Crossley wrote: Dave Fisher wrote: Hey Folks, Etch has graduated and is now a TLP, correct? It's board reports should now go directly to board@ from the PMC chair. As explained in the Incubator graduation docs, the Etch project needs to finalise their graduation steps. http://incubator.apache.org/clutch.html#etch http://incubator.apache.org/clutch.html#other http://incubator.apache.org/clutch.html#h-Graduate -David Regards, Dave Begin forwarded message: From: Marvin no-re...@apache.org Date: March 4, 2013 4:18:48 AM PST To: d...@etch.incubator.apache.org Subject: Incubator PMC/Board report for Mar 2013 ([ppmc]) Reply-To: d...@etch.apache.org delivered-to: mailing list d...@etch.apache.org delivered-to: moderator for d...@etch.apache.org Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 March 2013, 10:30:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Mar 6th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/March2013 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - 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 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Fwd: Incubator PMC/Board report for Mar 2013 ([ppmc])
Dave Fisher wrote: Hey Folks, Etch has graduated and is now a TLP, correct? It's board reports should now go directly to board@ from the PMC chair. As explained in the Incubator graduation docs, the Etch project needs to finalise their graduation steps. http://incubator.apache.org/clutch.html#etch http://incubator.apache.org/clutch.html#other http://incubator.apache.org/clutch.html#h-Graduate -David Regards, Dave Begin forwarded message: From: Marvin no-re...@apache.org Date: March 4, 2013 4:18:48 AM PST To: d...@etch.incubator.apache.org Subject: Incubator PMC/Board report for Mar 2013 ([ppmc]) Reply-To: d...@etch.apache.org delivered-to: mailing list d...@etch.apache.org delivered-to: moderator for d...@etch.apache.org Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 March 2013, 10:30:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Mar 6th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/March2013 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - 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: Incubator PMC/Board report for Mar 2013 ([ppmc])
These are for the new podlings Knox and Tez. The system has not yet detected that their mail lists are established. so the default is to general@ -David Marvin wrote: Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 March 2013, 10:30:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Mar 6th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/March2013 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - 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: Incubator PMC/Board report for Mar 2013 ([ppmc])
Daniel Shahaf wrote: @(tez|knox).incubator.apache.org lists had been created. Thanks. When Clutch detects that messages are flowing to the mbox then it flags the list as ready. They are not yet at the index page of http://mail-archives.apache.org/mod_mbox/ -David David Crossley wrote on Tue, Mar 05, 2013 at 09:04:11 +1100: These are for the new podlings Knox and Tez. The system has not yet detected that their mail lists are established. so the default is to general@ -David Marvin wrote: Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 March 2013, 10:30:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Mar 6th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/March2013 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - 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
Ripple, Streams, Onami, HDT need to fix your metadata
Ripple, Streams, Onami, Hadoop Development Tools ... Those projects would have received the email reminder about reporting. You need to care for your podling metadata in the content/podlings.xml file to take yourself off the monthly schedule and onto quarterly. (Unless you do want to keep doing monthly.) See column C and the help notes below the table: http://incubator.apache.org/clutch.html This file http://incubator.apache.org/report-groups.txt and http://incubator.apache.org/report_due_3.txt are generated from that content/podlings.xml file and are used to automate the reminders and other stuff. -David David Crossley wrote: Dave Fisher wrote: Hey Folks, Etch has graduated and is now a TLP, correct? It's board reports should now go directly to board@ from the PMC chair. As explained in the Incubator graduation docs, the Etch project needs to finalise their graduation steps. http://incubator.apache.org/clutch.html#etch http://incubator.apache.org/clutch.html#other http://incubator.apache.org/clutch.html#h-Graduate -David Regards, Dave Begin forwarded message: From: Marvin no-re...@apache.org Date: March 4, 2013 4:18:48 AM PST To: d...@etch.incubator.apache.org Subject: Incubator PMC/Board report for Mar 2013 ([ppmc]) Reply-To: d...@etch.apache.org delivered-to: mailing list d...@etch.apache.org delivered-to: moderator for d...@etch.apache.org Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 March 2013, 10:30:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Mar 6th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/March2013 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- Mentors should review reports for their project(s) and sign them off on the Incubator wiki page. Signing off reports shows that you are following the project - projects that are not signed may raise alarms for the Incubator PMC. Incubator PMC - 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: photark is still in the reporting schedule
Benson Margulies wrote: What did I miss in retiring it? I don't know. I added some missing things here: http://svn.apache.org/r1440870 http://incubator.apache.org/guides/retirement.html - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: photark is still in the reporting schedule
David Crossley wrote: Benson Margulies wrote: What did I miss in retiring it? I don't know. I added some missing things here: http://svn.apache.org/r1440870 http://incubator.apache.org/guides/retirement.html (Drat, leapt out on the outbox.) I meant to ask, why you think that there is an issue. This page seems okay: http://wiki.apache.org/incubator/February2013 and it is not in the lists at: http://incubator.apache.org/report-groups.txt -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: photark is still in the reporting schedule
David Crossley wrote: David Crossley wrote: Benson Margulies wrote: What did I miss in retiring it? I don't know. I added some missing things here: http://svn.apache.org/r1440870 http://incubator.apache.org/guides/retirement.html (Drat, leapt out on the outbox.) I meant to ask, why you think that there is an issue. This page seems okay: http://wiki.apache.org/incubator/February2013 Ah, i see that you recently edited that to remove Photark. My fix mentioned above was done on January 31. When does that shell of the wiki page get generated? and it is not in the lists at: http://incubator.apache.org/report-groups.txt That is regularly generated from content/podlings.xml file whenever that file is edited. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: marvin confused about schedules?
Ted Dunning wrote: The Drill project gets these reminders every month even though we are now into the quarterly reporting cycle (and our next report is in March). Is there a way to tell Marvin the real schedule? Reminders with 2/3 false alarm rate tend to get ignored. The metadata and scheduling for each project is in the hands of that project's group of developers. They need to care for their own entry in the content/podlings.xml file. They can compare their entry with other current podlings. -David -- Forwarded message -- From: Marvin no-re...@apache.org Date: Wed, Jan 30, 2013 at 9:11 AM Subject: Incubator PMC/Board report for Feb 2013 ([ppmc]) To: drill-...@incubator.apache.org Dear podling, This email was sent by an automated system on behalf of the Apache Incubator PMC. It is an initial reminder to give you plenty of time to prepare your quarterly board report. The board meeting is scheduled for Wed, 20 February 2013, 10:30:00:00 PST. The report for your podling will form a part of the Incubator PMC report. The Incubator PMC requires your report to be submitted 2 weeks before the board meeting, to allow sufficient time for review and submission (Wed, Feb 6th). Please submit your report with sufficient time to allow the incubator PMC, and subsequently board members to review and digest. Again, the very latest you should submit your report is 2 weeks prior to the board meeting. Thanks, The Apache Incubator PMC Submitting your Report -- Your report should contain the following: * Your project name * A brief description of your project, which assumes no knowledge of the project or necessarily of its field * A list of the three most important issues to address in the move towards graduation. * Any issues that the Incubator PMC or ASF Board might wish/need to be aware of * How has the community developed since the last report * How has the project developed since the last report. This should be appended to the Incubator Wiki page at: http://wiki.apache.org/incubator/February2013 Note: This manually populated. You may need to wait a little before this page is created from a template. Mentors --- - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Potential proposal + request volunteers for champion mentor roles - MetaModel
Kasper Sørensen wrote: Thank you for helping David. My username is KasperSorensen. Can someone please provide me access to create a new proposal wiki page on http://wiki.apache.org/incubator/ProjectProposals ? Done. -David - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Incubator voting status page
Branko Čibej wrote: sebb wrote: Branko Čibej wrote: Daniel Shahaf wrote: David Crossley wrote: You are striking the same type of problems that Clutch has needed to deal with over the years. In general, the state of podling metadata is not reliable. That is something that we need to get podling developers interested with. I have a current example. Flex and Wink haven't updated their podlings.xml entries to status=graduated , therefore certain infra scripts still consider them podlings rather than PMCs. These situations cause issues for other volunteers. Nor had PhotArk updated its entry to retired until I did that yesterday to get rid of one of the warnings. Those things usually mean that people have not followed the remainder of the steps for graduation or retirement. So i just leave them in that state to remind people. I'm not actually all that worried. The worst that can happen in the case of the voter script is that some votes don't get recorded, or are recorded later than expected. The script does emit warnings if it sees strangeness; I /could/ teach it to send the warnings to the podling's dev list (if known), cc: general@. But I'd rather not open the spam floodgates unless people really want me to. Clutch has been trying to flag those errors too. Occasionally i send some manual postings about these issues. Perhaps both tools listing the inconsistencies will assist. -David Why not append the errors to the end of the report? Good idea, I'll do that. -- Brane - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
