I wonder whether we really need this aspect of tracking participation. We already have a functional record of participation that cannot be tampered with in simrel contribution files. It should be simple to generate a report based on that and simrel contribution files represent the actual truth of what’s in the release…
- Konstantin ---------- Forwarded message ---------- From: Wayne Beaton <[email protected]> Date: Mon, Sep 9, 2013 at 10:09 AM Subject: [cross-project-issues-dev] Please announce your participation in Luna To: Cross project issues <[email protected]> Greetings folks. I've changed the way things work with regard to keeping track of who is participating in the simultaneous release. Previously, you just had to flip a bit in the project metadata; now, you have to announce your participation on the cross-project-issues-dev mailing list. This has several advantages: First, a project needs to have at least on representative as a member of the list to announce. This seems pretty obvious, but there have been multiple examples in the past of projects that were unaware of important messages and discussion because they didn't have this representation. Second, announcing on the list provides better transparency and openness. The community will have a much better chance of understanding what each participating project is doing and have a much more obvious opportunity to ask questions and otherwise participate. Third, it'll be harder for projects to "sneak in" after the fact. Believe it or not, there are multiple examples of projects who have "flipped the bit" on participation with older (past) releases. So... If you intend to participate in Luna, please do the following: * If you have not already done so, create a release record [1] for the release that you're contributing to Luna. Note that the Luna release date is June 25/2013. * Enter at least plan information for the release, minimally including a description and milestones. The release's description should minimally describe the main focus of the release. Please also consider adding a theme or two. This sort of information is really easy to add and update using the PMI. Note that you do not necessarily need to use the PMI for your plan, but please at least include a description of the release in the PMI record. * If you have not already done so, sign up for the cross-project-issues-dev mailing list * Send a note to cross-project-issues-dev with the name of your project, number of the release to include with Luna, and the offset (+0, +1, +2, ...). If you have any questions, please coordinate with your Planning Council representative [2], PMC, or me (via [email protected]). Thanks! Wayne [1] http://wiki.eclipse.org/Project_Management_Infrastructure/Project_Metadata#Releases [2] https://projects.eclipse.org/content/planning-council-representative -- Wayne Beaton Director of Open Source Projects, The Eclipse Foundation <http://www.eclipse.org> Learn about Eclipse Projects <http://www.eclipse.org/projects> <http://www.eclipsecon.org/europe2013> EclipseConEurope 2013 _______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev -- Cheers, Chris Aniszczyk http://aniszczyk.org +1 512 961 6719
_______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
