Re: Ivy mailing list organisation
On 10/13/07, Martijn Kruithof [EMAIL PROTECTED] wrote: [...] new proposal: notifications (gump, wiki, bugzilla, jira, wiki, svn, for both ivy and ant) dev (development discussion on both ivy and ant) ant-user ivy-user +1 Xavier Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://incubator.apache.org/ivy/ http://www.xoocode.org/
Re: Ivy mailing list organisation
On Sat, 13 Oct 2007, Martijn Kruithof [EMAIL PROTECTED] wrote: new proposal: notifications (gump, wiki, bugzilla, jira, wiki, svn, for both ivy and ant) dev (development discussion on both ivy and ant) ant-user ivy-user +1 Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ivy mailing list organisation
Martijn Kruithof wrote: Good points new proposal: notifications (gump, wiki, bugzilla, jira, wiki, svn, for both ivy and ant) dev (development discussion on both ivy and ant) ant-user ivy-user +1 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ivy mailing list organisation
Xavier Hanin schreef: On 10/12/07, Stefan Bodewig [EMAIL PROTECTED] wrote: On Fri, 12 Oct 2007, Martijn Kruithof [EMAIL PROTECTED] wrote: maybe we could create the following lists ant-bugs (gump, bugzilla, (what bug platform is ivy on?)) ant-commits (svn commits from both ivy and ant) ant-dev (development discussion on both ivy and ant) ant-user (as-is for the users) ivy-user (as-is for the users) works for me (but I probably wouldn't split bugs and commits at all). And instead of ant-dev, [EMAIL PROTECTED] as it is right now. Ivy uses JIRA and Xavier is the admin IIRC. Fine for me too, and I agree with Stefan, I wouldn't split bugs and commits. There's also yet another notification e-mail kind: wiki notifications. Where would they fall in? Good points new proposal: notifications (gump, wiki, bugzilla, jira, wiki, svn, for both ivy and ant) dev (development discussion on both ivy and ant) ant-user ivy-user Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: Ivy mailing list organisation
[EMAIL PROTECTED] schreef: maybe we could create the following lists ant-bugs (gump, bugzilla, (what bug platform is ivy on?)) ant-commits (svn commits from both ivy and ant) ant-dev (development discussion on both ivy and ant) ant-user (as-is for the users) ivy-user (as-is for the users) works for me (but I probably wouldn't split bugs and commits at all). And instead of ant-dev, [EMAIL PROTECTED] as it is right now. Ivy uses JIRA and Xavier is the admin IIRC. Fine for me too, and I agree with Stefan, I wouldn't split bugs and commits. There's also yet another notification e-mail kind: wiki notifications. Where would they fall in? Both projects (Ant and Ivy) have the same mail-origins. So we could also do: - wiki --- [EMAIL PROTECTED] [EMAIL PROTECTED] - bugtracking (Bugzilla + JIRA) --- [EMAIL PROTECTED] [EMAIL PROTECTED] - Users --- [EMAIL PROTECTED][EMAIL PROTECTED] - Developers--- [EMAIL PROTECTED] [EMAIL PROTECTED] - Usage of Gump --- [EMAIL PROTECTED] ([EMAIL PROTECTED]) maybe only one - Subversion--- [EMAIL PROTECTED] ([EMAIL PROTECTED]) maybe only one total 10-12 mailinglists Imo these are too many lists for the volume we have, furthermore in order to build a single development community, I'd really be in favour of only having one dev list. Of course everyone in the community can have his or her specific points of intrest and be more active in one part or the other, but we still are one development community. Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ivy mailing list organisation
2007/10/13, Martijn Kruithof [EMAIL PROTECTED]: new proposal: notifications (gump, wiki, bugzilla, jira, wiki, svn, for both ivy and ant) dev (development discussion on both ivy and ant) ant-user ivy-user +1 -- Gilles SCOKART
Re: Ivy mailing list organisation (Was: Re: Infrastructure (was Re: [RESULT] Ivy has Graduated as an Ant Subproject))
On 10/11/07, Dominique Devienne [EMAIL PROTECTED] wrote: On 10/11/07, Gilles Scokart [EMAIL PROTECTED] wrote: decide how we will organize our mailing list. [...] So, one solution is to keep it like that. Use three mailing list: - [EMAIL PROTECTED] (for user list) - [EMAIL PROTECTED] (for human dev related discussion) - [EMAIL PROTECTED] (for commit, jira and gump generated mails) What about using [EMAIL PROTECTED] and [EMAIL PROTECTED] directly, and discuss Ivy directly on the Ant lists? Ivy could be considered in a way as a big AntLib, and we don't have separate lists for AntLibs for example. Just a thought... --DD I don't really know what I think about that... On one hand, I think the traffic on Ivy mailing lists deserves its own mailing lists. Moreover there isn't much overlap between the subjects of both user lists: ivy-user is most of the time focused on dependency management discussion and not too much on ant related questions. One other (minor) thing I like is that in Ivy we have notifications e-mail separated from human traffic (ivy-commit vs ivy-dev), which is not the case in Ant, and I prefer keeping things separated. On the other hand, merging mailing lists would help ant users adopt ivy, and also help make the Ant+Ivy community a single and stronger community. So I don't know what I really prefer, maybe it's something we should ask to our (Ant and Ivy) users on our current user mailing list? Xavier - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://incubator.apache.org/ivy/ http://www.xoocode.org/
Re: Ivy mailing list organisation
Ho, and I also forgot the private mailing list. Do we need a separated list for ivy? I think not, but that depends probably more on you. Gilles 2007/10/12, Stefan Bodewig [EMAIL PROTECTED]: On Thu, 11 Oct 2007, Gilles Scokart [EMAIL PROTECTED] wrote: So, one solution is to keep it like that. Use three mailing list: - [EMAIL PROTECTED] (for user list) - [EMAIL PROTECTED] (for human dev related discussion) - [EMAIL PROTECTED] (for commit, jira and gump generated mails) that would be the easiest from an infrastructure point of view. The list could be renamed, existing subscribers would be transferred automatically and the old addresses would forward for some time. However, one of the drawback of this aproach is that we might often have to put dev@ant.apache.org and [EMAIL PROTECTED] in copy of our mails. True. This might call for a [EMAIL PROTECTED] list, but right now I don't think it will be needed that often. Dominique's suggestion would solve that easily, of course. I think the choice also depends on how will be made the votes for release, for new committers, or for other subjects. Release votes would be on the dev list of the subproject that wants to do the release, whichever that may be. Votes on people are not really conducted on public lists anyway, it just looks as if they were. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gilles SCOKART
Re: Ivy mailing list organisation
On Fri, 12 Oct 2007, Xavier Hanin [EMAIL PROTECTED] wrote: On 10/11/07, Dominique Devienne [EMAIL PROTECTED] wrote: What about using [EMAIL PROTECTED] and [EMAIL PROTECTED] directly, and discuss Ivy directly on the Ant lists? Ivy could be considered in a way as a big AntLib, and we don't have separate lists for AntLibs for example. Just a thought... --DD I don't really know what I think about that... Same here. So I don't know what I really prefer, maybe it's something we should ask to our (Ant and Ivy) users on our current user mailing list? That might be a good idea for users, but what about dev? We are the users here. I understand your wish to keep automatic mails and human generated content separate. Maybe we should do so for Ant as well? Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ivy mailing list organisation
On 10/12/07, Stefan Bodewig [EMAIL PROTECTED] wrote: On Fri, 12 Oct 2007, Martijn Kruithof [EMAIL PROTECTED] wrote: maybe we could create the following lists ant-bugs (gump, bugzilla, (what bug platform is ivy on?)) ant-commits (svn commits from both ivy and ant) ant-dev (development discussion on both ivy and ant) ant-user (as-is for the users) ivy-user (as-is for the users) works for me (but I probably wouldn't split bugs and commits at all). And instead of ant-dev, [EMAIL PROTECTED] as it is right now. Ivy uses JIRA and Xavier is the admin IIRC. Fine for me too, and I agree with Stefan, I wouldn't split bugs and commits. There's also yet another notification e-mail kind: wiki notifications. Where would they fall in? Xavier Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://incubator.apache.org/ivy/ http://www.xoocode.org/
Re: Ivy mailing list organisation
Stefan Bodewig schreef: On Fri, 12 Oct 2007, Xavier Hanin [EMAIL PROTECTED] wrote: On 10/11/07, Dominique Devienne [EMAIL PROTECTED] wrote: What about using [EMAIL PROTECTED] and [EMAIL PROTECTED] directly, and discuss Ivy directly on the Ant lists? Ivy could be considered in a way as a big AntLib, and we don't have separate lists for AntLibs for example. Just a thought... --DD I don't really know what I think about that... Same here. So I don't know what I really prefer, maybe it's something we should ask to our (Ant and Ivy) users on our current user mailing list? That might be a good idea for users, but what about dev? We are the users here. I understand your wish to keep automatic mails and human generated content separate. Maybe we should do so for Ant as well? Stefan I'd agree on separation of the commit messages for ant as well. volumes on september ivy-commits 119 ivy-dev 51 ivy-user 146 ant-dev 453 (48 gump, 113 svn, many bugzilla) ant-user 446 maybe we could create the following lists ant-bugs (gump, bugzilla, (what bug platform is ivy on?)) ant-commits (svn commits from both ivy and ant) ant-dev (development discussion on both ivy and ant) ant-user (as-is for the users) ivy-user (as-is for the users) br Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ivy mailing list organisation
On Fri, 12 Oct 2007, Gilles Scokart [EMAIL PROTECTED] wrote: Ho, and I also forgot the private mailing list. Do we need a separated list for ivy? No, there is no Ivy PPMC anymore. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ivy mailing list organisation
On Fri, 12 Oct 2007, Martijn Kruithof [EMAIL PROTECTED] wrote: maybe we could create the following lists ant-bugs (gump, bugzilla, (what bug platform is ivy on?)) ant-commits (svn commits from both ivy and ant) ant-dev (development discussion on both ivy and ant) ant-user (as-is for the users) ivy-user (as-is for the users) works for me (but I probably wouldn't split bugs and commits at all). And instead of ant-dev, [EMAIL PROTECTED] as it is right now. Ivy uses JIRA and Xavier is the admin IIRC. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Ivy mailing list organisation (Was: Re: Infrastructure (was Re: [RESULT] Ivy has Graduated as an Ant Subproject))
2007/10/11, Xavier Hanin [EMAIL PROTECTED]: On 10/11/07, Stefan Bodewig [EMAIL PROTECTED] wrote: We will at least need to: * migrate svn content * migrate the mailing lists * migrate the website * maybe migrate Wiki content * add the three Ivy committers to the ant Unix group. What can we do to help for these points? For the svn content, mailing lists and ant unix group, I don't see anything we can do. A thing that we should do is to decide how we will organize our mailing list. In the incubator, we had a user, a dev and a commit mailing list. I liked the separation of commit generated message and dev human messages because it make it much easier to read (you don't read both messages the same way). So, one solution is to keep it like that. Use three mailing list: - [EMAIL PROTECTED] (for user list) - [EMAIL PROTECTED] (for human dev related discussion) - [EMAIL PROTECTED] (for commit, jira and gump generated mails) However, one of the drawback of this aproach is that we might often have to put dev@ant.apache.org and [EMAIL PROTECTED] in copy of our mails. Which is something I personaly don't care when I'm using gmail (the mail are present only once) but that could be anoying with most other mailer. I think the choice also depends on how will be made the votes for release, for new committers, or for other subjects. WDYT? -- Gilles SCOKART
Re: Ivy mailing list organisation (Was: Re: Infrastructure (was Re: [RESULT] Ivy has Graduated as an Ant Subproject))
On 10/11/07, Gilles Scokart [EMAIL PROTECTED] wrote: decide how we will organize our mailing list. [...] So, one solution is to keep it like that. Use three mailing list: - [EMAIL PROTECTED] (for user list) - [EMAIL PROTECTED] (for human dev related discussion) - [EMAIL PROTECTED] (for commit, jira and gump generated mails) What about using [EMAIL PROTECTED] and [EMAIL PROTECTED] directly, and discuss Ivy directly on the Ant lists? Ivy could be considered in a way as a big AntLib, and we don't have separate lists for AntLibs for example. Just a thought... --DD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ivy mailing list organisation
On Thu, 11 Oct 2007, Gilles Scokart [EMAIL PROTECTED] wrote: So, one solution is to keep it like that. Use three mailing list: - [EMAIL PROTECTED] (for user list) - [EMAIL PROTECTED] (for human dev related discussion) - [EMAIL PROTECTED] (for commit, jira and gump generated mails) that would be the easiest from an infrastructure point of view. The list could be renamed, existing subscribers would be transferred automatically and the old addresses would forward for some time. However, one of the drawback of this aproach is that we might often have to put dev@ant.apache.org and [EMAIL PROTECTED] in copy of our mails. True. This might call for a [EMAIL PROTECTED] list, but right now I don't think it will be needed that often. Dominique's suggestion would solve that easily, of course. I think the choice also depends on how will be made the votes for release, for new committers, or for other subjects. Release votes would be on the dev list of the subproject that wants to do the release, whichever that may be. Votes on people are not really conducted on public lists anyway, it just looks as if they were. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
