You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by "Brian W. Fitzpatrick (JIRA)" <ji...@apache.org> on 2008/05/06 08:41:56 UTC
[jira] Created: (SHINDIG-237) Proposed COMMITTERS file for Shindig
Proposed COMMITTERS file for Shindig
------------------------------------
Key: SHINDIG-237
URL: https://issues.apache.org/jira/browse/SHINDIG-237
Project: Shindig
Issue Type: Improvement
Reporter: Brian W. Fitzpatrick
Priority: Trivial
Patch for creating COMMITTERS file
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Created: (SHINDIG-237) Proposed COMMITTERS file for Shindig
Posted by Kevin Brown <et...@google.com>.
On Tue, May 6, 2008 at 1:05 AM, Santiago Gala <sa...@gmail.com>
wrote:
> El mar, 06-05-2008 a las 01:46 -0500, Brian W. Fitzpatrick escribió:
> > Please see the issue attachment for the actual file in question.
> >
> > Note that this does not include the following committers from Google,
> > who I propose we remove from the project as they've not participated
> > (they have consented to be removed):
> >
> > bstoler Brian Stoler <bs...@google.com>
> > dcoker Doug Coker <dc...@google.com>
> > dglazer David Glazer <dg...@google.com>
> > dharkness David Harkness <dh...@google.com>
>
> David Harkness has actually committed:
> commit b7c5b19443007a17c50fcc6b75ba7a0ff2d413d5
> Author: David Harkness <dh...@apache.org>
> Date: Fri Jan 11 00:40:02 2008 +0000
>
Dave seems to have dropped off the face of the earth sometime in late
January. I'd be curious as to whether or not anyone has actually heard from
him since then.
>
>
> Added repository (code.google.com) and dependency for Caja.
>
>
> git-svn-id:
> https://svn.apache.org/repos/asf/incubator/shindig/trunk@611000
> 13f79535-47bb-0310-9956-ffa450edef68<ht...@61100013f79535-47bb-0310-9956-ffa450edef68>
> ---
> java/gadgets/pom.xml | 15 ++++++++++++++-
> 1 files changed, 14 insertions(+), 1 deletions(-)
>
> So I think he should be kept in the file, even if he is "emeritus" or
> something. Not sure about typical procedures for it.
>
>
>
>
> > gfs Graham Spencer <gf...@google.com>
> > jpanzer John Panzer <jp...@google.com>
> > ramani Ramkumar Ramani <ra...@google.com>
> > termie Andy Smith <te...@google.com>
> >
> > I'm not proposing any action for the following people, but they were
> > proposed committers from the official incubation proposal*, so we
> > should either get their CLAs and get them access or discuss removing
> > them as well, IMO:
> >
> > Jeffrey Regan (Google)
> > Jussi Myllymaki (Google)
> > Dan Farino (MySpace)
> > David Sklar (Ning)
> > Thomas Baker (Ning)
> > Tim Williamson (Ning)
> >
> > * http://markmail.org/message/6hed4akb4jefcdur
> >
>
> Also, their names are in <developer> tags in pom.xml files, so it would
> actually make sense to have the COMMITTERS generated from it or the
> other way around. If it is not judged worth the pain I can take care of
> both things and sync the current poms with the final COMMITTERS file.
>
> > -Fitz
> --
> Santiago Gala
> http://memojo.com/~sgala/blog/ <http://memojo.com/%7Esgala/blog/>
>
>
Re: [jira] Created: (SHINDIG-237) Proposed COMMITTERS file for
Shindig
Posted by Santiago Gala <sa...@gmail.com>.
El mar, 06-05-2008 a las 01:46 -0500, Brian W. Fitzpatrick escribió:
> Please see the issue attachment for the actual file in question.
>
> Note that this does not include the following committers from Google,
> who I propose we remove from the project as they've not participated
> (they have consented to be removed):
>
> bstoler Brian Stoler <bs...@google.com>
> dcoker Doug Coker <dc...@google.com>
> dglazer David Glazer <dg...@google.com>
> dharkness David Harkness <dh...@google.com>
David Harkness has actually committed:
commit b7c5b19443007a17c50fcc6b75ba7a0ff2d413d5
Author: David Harkness <dh...@apache.org>
Date: Fri Jan 11 00:40:02 2008 +0000
Added repository (code.google.com) and dependency for Caja.
git-svn-id:
https://svn.apache.org/repos/asf/incubator/shindig/trunk@611000
13f79535-47bb-0310-9956-ffa450edef68
---
java/gadgets/pom.xml | 15 ++++++++++++++-
1 files changed, 14 insertions(+), 1 deletions(-)
So I think he should be kept in the file, even if he is "emeritus" or
something. Not sure about typical procedures for it.
> gfs Graham Spencer <gf...@google.com>
> jpanzer John Panzer <jp...@google.com>
> ramani Ramkumar Ramani <ra...@google.com>
> termie Andy Smith <te...@google.com>
>
> I'm not proposing any action for the following people, but they were
> proposed committers from the official incubation proposal*, so we
> should either get their CLAs and get them access or discuss removing
> them as well, IMO:
>
> Jeffrey Regan (Google)
> Jussi Myllymaki (Google)
> Dan Farino (MySpace)
> David Sklar (Ning)
> Thomas Baker (Ning)
> Tim Williamson (Ning)
>
> * http://markmail.org/message/6hed4akb4jefcdur
>
Also, their names are in <developer> tags in pom.xml files, so it would
actually make sense to have the COMMITTERS generated from it or the
other way around. If it is not judged worth the pain I can take care of
both things and sync the current poms with the final COMMITTERS file.
> -Fitz
--
Santiago Gala
http://memojo.com/~sgala/blog/
Re: [jira] Created: (SHINDIG-237) Proposed COMMITTERS file for Shindig
Posted by Dan Peterson <dp...@google.com>.
On Mon, May 5, 2008 at 11:46 PM, Brian W. Fitzpatrick <fi...@google.com>
wrote:
> Please see the issue attachment for the actual file in question.
>
> Note that this does not include the following committers from Google,
> who I propose we remove from the project as they've not participated
> (they have consented to be removed):
>
> bstoler Brian Stoler <bs...@google.com>
> dcoker Doug Coker <dc...@google.com>
> dglazer David Glazer <dg...@google.com>
> dharkness David Harkness <dh...@google.com>
> gfs Graham Spencer <gf...@google.com>
> jpanzer John Panzer <jp...@google.com>
> ramani Ramkumar Ramani <ra...@google.com>
> termie Andy Smith <te...@google.com>
>
> I'm not proposing any action for the following people, but they were
> proposed committers from the official incubation proposal*, so we
> should either get their CLAs and get them access or discuss removing
> them as well, IMO:
>
> Jeffrey Regan (Google)
> Jussi Myllymaki (Google)
Jeffrey and Jussi have also both consented to being removed from the
committers list.
-Dan
> Dan Farino (MySpace)
> David Sklar (Ning)
> Thomas Baker (Ning)
> Tim Williamson (Ning)
>
> * http://markmail.org/message/6hed4akb4jefcdur
>
> -Fitz
>
Re: [jira] Created: (SHINDIG-237) Proposed COMMITTERS file for Shindig
Posted by "Brian W. Fitzpatrick" <fi...@google.com>.
Please see the issue attachment for the actual file in question.
Note that this does not include the following committers from Google,
who I propose we remove from the project as they've not participated
(they have consented to be removed):
bstoler Brian Stoler <bs...@google.com>
dcoker Doug Coker <dc...@google.com>
dglazer David Glazer <dg...@google.com>
dharkness David Harkness <dh...@google.com>
gfs Graham Spencer <gf...@google.com>
jpanzer John Panzer <jp...@google.com>
ramani Ramkumar Ramani <ra...@google.com>
termie Andy Smith <te...@google.com>
I'm not proposing any action for the following people, but they were
proposed committers from the official incubation proposal*, so we
should either get their CLAs and get them access or discuss removing
them as well, IMO:
Jeffrey Regan (Google)
Jussi Myllymaki (Google)
Dan Farino (MySpace)
David Sklar (Ning)
Thomas Baker (Ning)
Tim Williamson (Ning)
* http://markmail.org/message/6hed4akb4jefcdur
-Fitz
[jira] Commented: (SHINDIG-237) Proposed COMMITTERS file for
Shindig
Posted by "Brian W. Fitzpatrick (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594670#action_12594670 ]
Brian W. Fitzpatrick commented on SHINDIG-237:
----------------------------------------------
Vincent: If you wish to submit a patch to update the pom and a script to generate the COMMITTER file, and the rest of the committers prefer it, then go right ahead, but otherwise, I'd like to just submit this as-is.
> Proposed COMMITTERS file for Shindig
> ------------------------------------
>
> Key: SHINDIG-237
> URL: https://issues.apache.org/jira/browse/SHINDIG-237
> Project: Shindig
> Issue Type: Improvement
> Reporter: Brian W. Fitzpatrick
> Priority: Trivial
> Attachments: COMMITTERS
>
>
> Patch for creating COMMITTERS file
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-237) Proposed COMMITTERS file for
Shindig
Posted by "Vincent Siveton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595062#action_12595062 ]
Vincent Siveton commented on SHINDIG-237:
-----------------------------------------
Brian: no time right now to make a patch for this one. So feel free to commit it but leave this issue open.
Maybe someone or me could create a acript, a Ant task or an XSLT to do it...
> Proposed COMMITTERS file for Shindig
> ------------------------------------
>
> Key: SHINDIG-237
> URL: https://issues.apache.org/jira/browse/SHINDIG-237
> Project: Shindig
> Issue Type: Improvement
> Reporter: Brian W. Fitzpatrick
> Priority: Trivial
> Attachments: COMMITTERS
>
>
> Patch for creating COMMITTERS file
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-237) Proposed COMMITTERS file for
Shindig
Posted by "Cassie Doll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595658#action_12595658 ]
Cassie Doll commented on SHINDIG-237:
-------------------------------------
fantastical. this script works for me so I am going to check it in along with the newly generated committers file. i went through and cleaned up the pom.xml members to reflect all of the threads as well. just two things perhaps for a next patch
1. you have to specify the -Dbuild.directory=. when calling the mvn command. (i also had to use mvn -Pto-committers..)
2. The file generated needs a newline at the bottom of it
I tried fixing these things with simple modifications.. it didn't work right away so I left it alone for now :)
anyway, thanks vincent!
> Proposed COMMITTERS file for Shindig
> ------------------------------------
>
> Key: SHINDIG-237
> URL: https://issues.apache.org/jira/browse/SHINDIG-237
> Project: Shindig
> Issue Type: Improvement
> Reporter: Brian W. Fitzpatrick
> Priority: Trivial
> Attachments: COMMITTERS, SHINDIG-237.patch
>
>
> Patch for creating COMMITTERS file
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-237) Proposed COMMITTERS file for
Shindig
Posted by "Santiago Gala (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594632#action_12594632 ]
Santiago Gala commented on SHINDIG-237:
---------------------------------------
The text file is good enough unless we use the pom for other things (docs, etc.) then it is important to have them in sync.
My idea is that we have the plain text as master and remove committers from the POM, until there is a need to have them there, and then a script would take care of synchronizing both.
> Proposed COMMITTERS file for Shindig
> ------------------------------------
>
> Key: SHINDIG-237
> URL: https://issues.apache.org/jira/browse/SHINDIG-237
> Project: Shindig
> Issue Type: Improvement
> Reporter: Brian W. Fitzpatrick
> Priority: Trivial
> Attachments: COMMITTERS
>
>
> Patch for creating COMMITTERS file
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-237) Proposed COMMITTERS file for
Shindig
Posted by "Vincent Siveton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594641#action_12594641 ]
Vincent Siveton commented on SHINDIG-237:
-----------------------------------------
Link to Incubator Guides
http://incubator.apache.org/guides/
http://incubator.apache.org/guides/mentor.html#build-clean-up
"Update developers to use apache IDs"
> Proposed COMMITTERS file for Shindig
> ------------------------------------
>
> Key: SHINDIG-237
> URL: https://issues.apache.org/jira/browse/SHINDIG-237
> Project: Shindig
> Issue Type: Improvement
> Reporter: Brian W. Fitzpatrick
> Priority: Trivial
> Attachments: COMMITTERS
>
>
> Patch for creating COMMITTERS file
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-237) Proposed COMMITTERS file for
Shindig
Posted by "Santiago Gala (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597715#action_12597715 ]
Santiago Gala commented on SHINDIG-237:
---------------------------------------
I'd say the patch submitted was violating the request of having the COMMITTERS file, plain text and easy to understand and edit as data "master", and the generated POM as "slave".
In addition it uses xslt for the extraction, which is one of the most difficult to handle programming languages that a human mind has invented.
I don't care that much about it, but it is wrong, and it took me a lot of time to notice: Chris Chabot is not a PPMC member (yet), There are possibly more bugs on it, but inspecting an XML file is tiring. Also, but this is a minor one, it generates extra whitespace at the end of the line, after the roles
I'm -1 on this change and would stick to the original proposal by fitz: a text file as data master and using a script to parse it into a machine usable XML, just on the grounds of the time that is taking me to find where the bug in the Chris role and the whitespace handling is.
> Proposed COMMITTERS file for Shindig
> ------------------------------------
>
> Key: SHINDIG-237
> URL: https://issues.apache.org/jira/browse/SHINDIG-237
> Project: Shindig
> Issue Type: Improvement
> Reporter: Brian W. Fitzpatrick
> Assignee: Cassie Doll
> Priority: Trivial
> Attachments: COMMITTERS, SHINDIG-237.patch
>
>
> Patch for creating COMMITTERS file
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-237) Proposed COMMITTERS file for
Shindig
Posted by "Cassie Doll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594635#action_12594635 ]
Cassie Doll commented on SHINDIG-237:
-------------------------------------
+1
> Proposed COMMITTERS file for Shindig
> ------------------------------------
>
> Key: SHINDIG-237
> URL: https://issues.apache.org/jira/browse/SHINDIG-237
> Project: Shindig
> Issue Type: Improvement
> Reporter: Brian W. Fitzpatrick
> Priority: Trivial
> Attachments: COMMITTERS
>
>
> Patch for creating COMMITTERS file
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-237) Proposed COMMITTERS file for
Shindig
Posted by "Vincent Siveton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594561#action_12594561 ]
Vincent Siveton commented on SHINDIG-237:
-----------------------------------------
Since the parent POM already contains this list, IMHO this file is useless
> Proposed COMMITTERS file for Shindig
> ------------------------------------
>
> Key: SHINDIG-237
> URL: https://issues.apache.org/jira/browse/SHINDIG-237
> Project: Shindig
> Issue Type: Improvement
> Reporter: Brian W. Fitzpatrick
> Priority: Trivial
> Attachments: COMMITTERS
>
>
> Patch for creating COMMITTERS file
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-237) Proposed COMMITTERS file for
Shindig
Posted by "Vincent Siveton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594638#action_12594638 ]
Vincent Siveton commented on SHINDIG-237:
-----------------------------------------
I understand the readingness concern and the PHP arguments...
I suggest an other approach for the sync: POM to COMMITTERS file instead of the opposite. I guess it will be easy to include a profile with maven-antrun-plugin and echo task to write the committers file...
Also, having a POM project (i.e. with generic project information like name, description, issueManagement, developers...) is always a good practice in Maven land.
Brian: it will be easy to update roles in the POM, so IMHO it is not a big issue
Kevin: I don't think it is an ASF requirement or incubator rule, but it will be probably safe to ask general@incubator
> Proposed COMMITTERS file for Shindig
> ------------------------------------
>
> Key: SHINDIG-237
> URL: https://issues.apache.org/jira/browse/SHINDIG-237
> Project: Shindig
> Issue Type: Improvement
> Reporter: Brian W. Fitzpatrick
> Priority: Trivial
> Attachments: COMMITTERS
>
>
> Patch for creating COMMITTERS file
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SHINDIG-237) Proposed COMMITTERS file for Shindig
Posted by "Cassie Doll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Cassie Doll resolved SHINDIG-237.
---------------------------------
Resolution: Fixed
Assignee: Cassie Doll
> Proposed COMMITTERS file for Shindig
> ------------------------------------
>
> Key: SHINDIG-237
> URL: https://issues.apache.org/jira/browse/SHINDIG-237
> Project: Shindig
> Issue Type: Improvement
> Reporter: Brian W. Fitzpatrick
> Assignee: Cassie Doll
> Priority: Trivial
> Attachments: COMMITTERS, SHINDIG-237.patch
>
>
> Patch for creating COMMITTERS file
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-237) Proposed COMMITTERS file for
Shindig
Posted by "Santiago Gala (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594565#action_12594565 ]
Santiago Gala commented on SHINDIG-237:
---------------------------------------
Agreed with Cassie, I'm trying to think of a reasonable way to make a script to sync COMMITTERS into the xml without bringing in unreasonable requirements. The xml is used by maven to generate docs, so we will need to keep up to date if maven documents are to be used (I can't believe /me is writing this!).
Maybe I could write a small python script, commit it, and use it from time to time to re-sync this part of the pom.
Any answer from Fitz on how to typically treat the "inactive/emeritus" committers? Not sure about how other projects manage this. A separate list? data columns? a field?...
> Proposed COMMITTERS file for Shindig
> ------------------------------------
>
> Key: SHINDIG-237
> URL: https://issues.apache.org/jira/browse/SHINDIG-237
> Project: Shindig
> Issue Type: Improvement
> Reporter: Brian W. Fitzpatrick
> Priority: Trivial
> Attachments: COMMITTERS
>
>
> Patch for creating COMMITTERS file
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-237) Proposed COMMITTERS file for
Shindig
Posted by "Kevin Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594627#action_12594627 ]
Kevin Brown commented on SHINDIG-237:
-------------------------------------
Santigo: Is this even relevant? If there's no legal requirement or ASF requirement for having committers in the pom, I'd prefer to just have the simple text file. If people really want to know who is committing, there's always the SVN history anyway.
> Proposed COMMITTERS file for Shindig
> ------------------------------------
>
> Key: SHINDIG-237
> URL: https://issues.apache.org/jira/browse/SHINDIG-237
> Project: Shindig
> Issue Type: Improvement
> Reporter: Brian W. Fitzpatrick
> Priority: Trivial
> Attachments: COMMITTERS
>
>
> Patch for creating COMMITTERS file
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-237) Proposed COMMITTERS file for
Shindig
Posted by "Santiago Gala (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594510#action_12594510 ]
Santiago Gala commented on SHINDIG-237:
---------------------------------------
I just paste the contents of "git shortlog -s -e" on the repository for reference, as of
$ LC_ALL=C TZ=UTC date
Tue May 6 08:10:17 UTC 2008
5 Brian MacCallister <br...@apache.org>
126 Cassie Doll <do...@apache.org>
3 Chris Chabot <ch...@apache.org>
2 Daniel Bentley <db...@apache.org>
1 David Harkness <dh...@apache.org>
1 Greg Stein <gs...@apache.org>
13 John Hjelmstad <jo...@apache.org>
103 Kevin Brown <et...@apache.org>
13 Louis Ryan <lr...@apache.org>
87 Paul Lindner <li...@apache.org>
11 Santiago Gala <sg...@apache.org>
44 Zhen Wang <zh...@apache.org>
> Proposed COMMITTERS file for Shindig
> ------------------------------------
>
> Key: SHINDIG-237
> URL: https://issues.apache.org/jira/browse/SHINDIG-237
> Project: Shindig
> Issue Type: Improvement
> Reporter: Brian W. Fitzpatrick
> Priority: Trivial
> Attachments: COMMITTERS
>
>
> Patch for creating COMMITTERS file
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-237) Proposed COMMITTERS file for
Shindig
Posted by "Brian W. Fitzpatrick (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594579#action_12594579 ]
Brian W. Fitzpatrick commented on SHINDIG-237:
----------------------------------------------
Vincent: While I appreciate your kind words, I beg to differ. The POM doesn't include mentors and non-java committers, nor is it easily readable at a glance by a human being.
Santiago: Typically, just add a section at the bottom titled "Emeritus committers".
> Proposed COMMITTERS file for Shindig
> ------------------------------------
>
> Key: SHINDIG-237
> URL: https://issues.apache.org/jira/browse/SHINDIG-237
> Project: Shindig
> Issue Type: Improvement
> Reporter: Brian W. Fitzpatrick
> Priority: Trivial
> Attachments: COMMITTERS
>
>
> Patch for creating COMMITTERS file
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-237) Proposed COMMITTERS file for Shindig
Posted by "Vincent Siveton (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vincent Siveton updated SHINDIG-237:
------------------------------------
Attachment: SHINDIG-237.patch
This patch includes:
* an xsl which creates a text file similar to the Brian's one
* created a new profile in pom (called "to-committers") to generate a COMMITTERS file using this xsl. Just call "mvn to-committers" to generate it.
* updated the committer list in the pom with the informations I have (need to review it, I am lost between jira and mailing list comments... IMHO we need to forbid mail replies on any jira issues, just log comments in one space ie JIRA, just my 2 cents.)
> Proposed COMMITTERS file for Shindig
> ------------------------------------
>
> Key: SHINDIG-237
> URL: https://issues.apache.org/jira/browse/SHINDIG-237
> Project: Shindig
> Issue Type: Improvement
> Reporter: Brian W. Fitzpatrick
> Priority: Trivial
> Attachments: COMMITTERS, SHINDIG-237.patch
>
>
> Patch for creating COMMITTERS file
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SHINDIG-237) Proposed COMMITTERS file for
Shindig
Posted by "Cassie Doll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594563#action_12594563 ]
Cassie Doll commented on SHINDIG-237:
-------------------------------------
The parent pom is only for the java version though, not php. Can we get rid of the pom committers altogether and just use a specific file? A file is easier to manage than the extremely large xml as well.
> Proposed COMMITTERS file for Shindig
> ------------------------------------
>
> Key: SHINDIG-237
> URL: https://issues.apache.org/jira/browse/SHINDIG-237
> Project: Shindig
> Issue Type: Improvement
> Reporter: Brian W. Fitzpatrick
> Priority: Trivial
> Attachments: COMMITTERS
>
>
> Patch for creating COMMITTERS file
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SHINDIG-237) Proposed COMMITTERS file for Shindig
Posted by "Brian W. Fitzpatrick (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SHINDIG-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian W. Fitzpatrick updated SHINDIG-237:
-----------------------------------------
Attachment: COMMITTERS
to be put in /trunk
> Proposed COMMITTERS file for Shindig
> ------------------------------------
>
> Key: SHINDIG-237
> URL: https://issues.apache.org/jira/browse/SHINDIG-237
> Project: Shindig
> Issue Type: Improvement
> Reporter: Brian W. Fitzpatrick
> Priority: Trivial
> Attachments: COMMITTERS
>
>
> Patch for creating COMMITTERS file
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.