Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
Yep. What we would need to know is the from address on the commit emails, so we know what address to subscribe. I changed the email from public to moderated so I could discover the sender: [EMAIL PROTECTED] You'd think Google would have figured this stuff out already :-). Yes but its a work in progress so we will let it slide. I suspect we want minimal barriers to participation here, so I'd throw it open. We can change things later if we get too much spam etc. Google is warning about spam if you leave it wide open but I guess we can deal with that when the time comes. In particular, we should set the group to accept public email (it took my test message submitted via the web interface, but not the one I emailed from my gmail account). That should at least make the commit emails work, so we can see what the right from address is. That's weird taht you could only send email from your interface. Can you send again from your gmail account to test if its moderated or not? I changed you to owner as well so you can have the dubious honor of assisting in the group management. Go ahead an change it to wide open public email once you test your gmail again. Craig Sean
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
Lets think on the package names a bit. OK. What about just org.shale? So for petstore we have org.shale.petstore as the package name with org.shale as the maven group name. Craig Sean
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
I prefer com.google.shalegoodies Your thoughts? -- James Mitchell 678.910.8017 On Aug 4, 2006, at 11:30 AM, Sean Schofield wrote: Lets think on the package names a bit. OK. What about just org.shale? So for petstore we have org.shale.petstore as the package name with org.shale as the maven group name. Craig Sean
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
I think I prefer that too. shale.org doesn't appeal to me for some reason I can't really put my finger on. Greg On Aug 4, 2006, at 2:03 PM, James Mitchell wrote: I prefer com.google.shalegoodies Your thoughts? -- James Mitchell 678.910.8017 On Aug 4, 2006, at 11:30 AM, Sean Schofield wrote: Lets think on the package names a bit. OK. What about just org.shale? So for petstore we have org.shale.petstore as the package name with org.shale as the maven group name. Craig Sean
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
The only problem with com.google is if we move it from being hosted on google.com (a distinct possibility at this point.) Sean On 8/4/06, Greg Reddin [EMAIL PROTECTED] wrote: I think I prefer that too. shale.org doesn't appeal to me for some reason I can't really put my finger on. Greg On Aug 4, 2006, at 2:03 PM, James Mitchell wrote: I prefer com.google.shalegoodies Your thoughts? -- James Mitchell 678.910.8017 On Aug 4, 2006, at 11:30 AM, Sean Schofield wrote: Lets think on the package names a bit. OK. What about just org.shale? So for petstore we have org.shale.petstore as the package name with org.shale as the maven group name. Craig Sean
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
On 8/4/06, Sean Schofield [EMAIL PROTECTED] wrote: The only problem with com.google is if we move it from being hosted on google.com (a distinct possibility at this point.) shale.goodies.petstore ? -- Wendy
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
I'm cool with that too. It doesn't have to be a web address :-) Greg On Aug 4, 2006, at 2:47 PM, Wendy Smoak wrote: On 8/4/06, Sean Schofield [EMAIL PROTECTED] wrote: The only problem with com.google is if we move it from being hosted on google.com (a distinct possibility at this point.) shale.goodies.petstore ? -- Wendy
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
shale.goodies.petstore ? I like it except for one problem. What is the maven group id? If it starts with shale, people browsing ibiblio might get confused and wonder where the rest of the stuff is? Wendy Sean
Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
I'm considering an option that Craig mentioned earlier - moving this to google's new open source area. While I understand the reasons for the tight restrictions that ASF has, it makes it difficult to host a fully functional sample app using several different technologies. On google (and presumably dev.java.net), we can also distribute binaries wither hibernate, etc. That will allow more people to use the app. No matter how easy you make it, some people are just putoff by compiling their own source. I admit, sometimes I fall into this category (if my interest is only casual.) If we do move it, I'd still like some loose integration between shale and this project. This would include links to the shale-petstore from the shale site and referring people on the user list to the shale-petstore when it serves as an appropriate example. Thoughts? Sean On 8/3/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 8/3/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 8/3/06, Sean Schofield [EMAIL PROTECTED] wrote: Most of the images seem to be: GNU Free Documentation License, Version 1.2. What about the text? Any ideas on that? Are you asking about the text on Wikipedia? There's a notice at the bottom of every page: All text is available under the terms of the GNU Free Documentation License. As for whether we can use the text or images, if GFDL is not listed on Cliff's page [1] then I would ask on [EMAIL PROTECTED] I suspect the GNU license for docs will have issues, so asking on legal-discuss would be a good idea. In the mean time, note that the original Blueprints PetStore application (including content and images) is BSD-licensed, so we can use stuff from there. https://blueprints.dev.java.net) Craig [1] http://people.apache.org/~cliffs/3party.html -- Wendy
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
What about just adding shale-petstore as part of shale-goodies? Was that just a thing of getting wires crossed or did you intend for it to be a separate project? Greg On Aug 3, 2006, at 2:26 PM, Sean Schofield wrote: And I just set up a shale-petstore ;-) Do you envision this being more then the petstore app? Also, are we sure we want google as opposed to dev.java.net? I don't know much about the google option. It seems like we can have discussion via a google group. What about distribution of jar files? Sean On 8/3/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 8/3/06, Greg Reddin [EMAIL PROTECTED] wrote: +1. I was wanting to figure out what all that google open source stuff was about anyway. But I'm cool with either google or java.net. I just set up shale-goodies for us at Google[1]. Note that you must have a GMail account to log in with for SVN access, but that's already true for a bunch of us. Send me your GMail username and I'll add you in as a project owner. Greg Craig [1] http://code.google.com/p/shale-goodies/ On Aug 3, 2006, at 1:25 PM, Sean Schofield wrote: I'm considering an option that Craig mentioned earlier - moving this to google's new open source area. While I understand the reasons for the tight restrictions that ASF has, it makes it difficult to host a fully functional sample app using several different technologies. On google (and presumably dev.java.net), we can also distribute binaries wither hibernate, etc. That will allow more people to use the app. No matter how easy you make it, some people are just putoff by compiling their own source. I admit, sometimes I fall into this category (if my interest is only casual.) If we do move it, I'd still like some loose integration between shale and this project. This would include links to the shale- petstore from the shale site and referring people on the user list to the shale-petstore when it serves as an appropriate example. Thoughts? Sean On 8/3/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 8/3/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 8/3/06, Sean Schofield [EMAIL PROTECTED] wrote: Most of the images seem to be: GNU Free Documentation License, Version 1.2. What about the text? Any ideas on that? Are you asking about the text on Wikipedia? There's a notice at the bottom of every page: All text is available under the terms of the GNU Free Documentation License. As for whether we can use the text or images, if GFDL is not listed on Cliff's page [1] then I would ask on [EMAIL PROTECTED] I suspect the GNU license for docs will have issues, so asking on legal-discuss would be a good idea. In the mean time, note that the original Blueprints PetStore application (including content and images) is BSD-licensed, so we can use stuff from there. https://blueprints.dev.java.net) Craig [1] http://people.apache.org/~cliffs/3party.html -- Wendy
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
On 8/3/06, Greg Reddin [EMAIL PROTECTED] wrote: What about just adding shale-petstore as part of shale-goodies? Was that just a thing of getting wires crossed or did you intend for it to be a separate project? It was definitely great minds thinking alike at the same time ... :-) I think we would want to set up a playground where multiple libraries or examples could be hosted, rather than a separate one for each, so we can use it for a little community building too. Re: Google vs java.net, I confess to the same curiousity Greg mentioned about the new features. Yes, you can use a Google Group for discussion. No, they don't have an answer for binary distros yet, but that's definitely something theiy are working on. Greg Craig On Aug 3, 2006, at 2:26 PM, Sean Schofield wrote: And I just set up a shale-petstore ;-) Do you envision this being more then the petstore app? Also, are we sure we want google as opposed to dev.java.net? I don't know much about the google option. It seems like we can have discussion via a google group. What about distribution of jar files? Sean On 8/3/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 8/3/06, Greg Reddin [EMAIL PROTECTED] wrote: +1. I was wanting to figure out what all that google open source stuff was about anyway. But I'm cool with either google or java.net. I just set up shale-goodies for us at Google[1]. Note that you must have a GMail account to log in with for SVN access, but that's already true for a bunch of us. Send me your GMail username and I'll add you in as a project owner. Greg Craig [1] http://code.google.com/p/shale-goodies/ On Aug 3, 2006, at 1:25 PM, Sean Schofield wrote: I'm considering an option that Craig mentioned earlier - moving this to google's new open source area. While I understand the reasons for the tight restrictions that ASF has, it makes it difficult to host a fully functional sample app using several different technologies. On google (and presumably dev.java.net), we can also distribute binaries wither hibernate, etc. That will allow more people to use the app. No matter how easy you make it, some people are just putoff by compiling their own source. I admit, sometimes I fall into this category (if my interest is only casual.) If we do move it, I'd still like some loose integration between shale and this project. This would include links to the shale- petstore from the shale site and referring people on the user list to the shale-petstore when it serves as an appropriate example. Thoughts? Sean On 8/3/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 8/3/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 8/3/06, Sean Schofield [EMAIL PROTECTED] wrote: Most of the images seem to be: GNU Free Documentation License, Version 1.2. What about the text? Any ideas on that? Are you asking about the text on Wikipedia? There's a notice at the bottom of every page: All text is available under the terms of the GNU Free Documentation License. As for whether we can use the text or images, if GFDL is not listed on Cliff's page [1] then I would ask on [EMAIL PROTECTED] I suspect the GNU license for docs will have issues, so asking on legal-discuss would be a good idea. In the mean time, note that the original Blueprints PetStore application (including content and images) is BSD-licensed, so we can use stuff from there. https://blueprints.dev.java.net) Craig [1] http://people.apache.org/~cliffs/3party.html -- Wendy
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
Mine is [EMAIL PROTECTED], but please don't make me the owner -- too much responsibility. Unless 'owner' is the same as committer? -- James Mitchell 678.910.8017 On Aug 3, 2006, at 3:08 PM, Craig McClanahan wrote: On 8/3/06, Greg Reddin [EMAIL PROTECTED] wrote: +1. I was wanting to figure out what all that google open source stuff was about anyway. But I'm cool with either google or java.net. I just set up shale-goodies for us at Google[1]. Note that you must have a GMail account to log in with for SVN access, but that's already true for a bunch of us. Send me your GMail username and I'll add you in as a project owner. Greg Craig [1] http://code.google.com/p/shale-goodies/ On Aug 3, 2006, at 1:25 PM, Sean Schofield wrote: I'm considering an option that Craig mentioned earlier - moving this to google's new open source area. While I understand the reasons for the tight restrictions that ASF has, it makes it difficult to host a fully functional sample app using several different technologies. On google (and presumably dev.java.net), we can also distribute binaries wither hibernate, etc. That will allow more people to use the app. No matter how easy you make it, some people are just putoff by compiling their own source. I admit, sometimes I fall into this category (if my interest is only casual.) If we do move it, I'd still like some loose integration between shale and this project. This would include links to the shale- petstore from the shale site and referring people on the user list to the shale-petstore when it serves as an appropriate example. Thoughts? Sean On 8/3/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 8/3/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 8/3/06, Sean Schofield [EMAIL PROTECTED] wrote: Most of the images seem to be: GNU Free Documentation License, Version 1.2. What about the text? Any ideas on that? Are you asking about the text on Wikipedia? There's a notice at the bottom of every page: All text is available under the terms of the GNU Free Documentation License. As for whether we can use the text or images, if GFDL is not listed on Cliff's page [1] then I would ask on [EMAIL PROTECTED] I suspect the GNU license for docs will have issues, so asking on legal-discuss would be a good idea. In the mean time, note that the original Blueprints PetStore application (including content and images) is BSD-licensed, so we can use stuff from there. https://blueprints.dev.java.net) Craig [1] http://people.apache.org/~cliffs/3party.html -- Wendy
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
On 8/3/06, James Mitchell [EMAIL PROTECTED] wrote: Mine is [EMAIL PROTECTED], but please don't make me the owner -- too much responsibility. Unless 'owner' is the same as committer? The only difference between project owner and project member is access to the admin screens for the project itself. Both have commit rights. I'll set you as a member if you want just that. -- James Mitchell 678.910.8017 Craig On Aug 3, 2006, at 3:08 PM, Craig McClanahan wrote: On 8/3/06, Greg Reddin [EMAIL PROTECTED] wrote: +1. I was wanting to figure out what all that google open source stuff was about anyway. But I'm cool with either google or java.net. I just set up shale-goodies for us at Google[1]. Note that you must have a GMail account to log in with for SVN access, but that's already true for a bunch of us. Send me your GMail username and I'll add you in as a project owner. Greg Craig [1] http://code.google.com/p/shale-goodies/ On Aug 3, 2006, at 1:25 PM, Sean Schofield wrote: I'm considering an option that Craig mentioned earlier - moving this to google's new open source area. While I understand the reasons for the tight restrictions that ASF has, it makes it difficult to host a fully functional sample app using several different technologies. On google (and presumably dev.java.net), we can also distribute binaries wither hibernate, etc. That will allow more people to use the app. No matter how easy you make it, some people are just putoff by compiling their own source. I admit, sometimes I fall into this category (if my interest is only casual.) If we do move it, I'd still like some loose integration between shale and this project. This would include links to the shale- petstore from the shale site and referring people on the user list to the shale-petstore when it serves as an appropriate example. Thoughts? Sean On 8/3/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 8/3/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 8/3/06, Sean Schofield [EMAIL PROTECTED] wrote: Most of the images seem to be: GNU Free Documentation License, Version 1.2. What about the text? Any ideas on that? Are you asking about the text on Wikipedia? There's a notice at the bottom of every page: All text is available under the terms of the GNU Free Documentation License. As for whether we can use the text or images, if GFDL is not listed on Cliff's page [1] then I would ask on [EMAIL PROTECTED] I suspect the GNU license for docs will have issues, so asking on legal-discuss would be a good idea. In the mean time, note that the original Blueprints PetStore application (including content and images) is BSD-licensed, so we can use stuff from there. https://blueprints.dev.java.net) Craig [1] http://people.apache.org/~cliffs/3party.html -- Wendy
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
On 8/3/06, Craig McClanahan [EMAIL PROTECTED] wrote: The only difference between project owner and project member is access to the admin screens for the project itself. Both have commit rights. I'll set you as a member if you want just that. I didn't know that was an option. Just 'member' will be fine for me, too. Thanks, Wendy
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
I'm ok with shale-goodies as long as we can release artifacts as different versions, etc. I'm assuming that's the case. I think we're all curious about the google option so lets go ahead with it. We can always move it in a few months if it doesn't pan out. Right now there;s just shale-petstore and it wouldn't be the end of the world to lose the svn history if we had to move it. my gmail is sean.schofield Sean ps. Google is also doing something cool which is allowing you to host your domain email through them. There is a beta test going on and they accepted my application. Something to consider for folks who have their own domain for business purposes. On 8/3/06, Wendy Smoak [EMAIL PROTECTED] wrote: On 8/3/06, Craig McClanahan [EMAIL PROTECTED] wrote: The only difference between project owner and project member is access to the admin screens for the project itself. Both have commit rights. I'll set you as a member if you want just that. I didn't know that was an option. Just 'member' will be fine for me, too. Thanks, Wendy
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
Any reason why we can't use org.apache.shale for the package names still? I can't really think of a better package name off hand. Sean On 8/3/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 8/3/06, Sean Schofield [EMAIL PROTECTED] wrote: I'm ok with shale-goodies as long as we can release artifacts as different versions, etc. I'm assuming that's the case. I think we're all curious about the google option so lets go ahead with it. We can always move it in a few months if it doesn't pan out. Right now there;s just shale-petstore and it wouldn't be the end of the world to lose the svn history if we had to move it. I set up a maven/trunk/master-pom analogous to what we have in the Apache repository ... you could set up shale-petstore/trunk to make it independently branchable and so on. We could even set up a current externals later. We'll have to think about the package names (and Maven artifact ids) here ... I used shale-goodies:shale-goodies:1-SNAPSHOT for the initial master pom, but haven't checked in any code yet. my gmail is sean.schofield Added. Sean ps. Google is also doing something cool which is allowing you to host your domain email through them. There is a beta test going on and they accepted my application. Something to consider for folks who have their own domain for business purposes. That is pretty cool. Craig
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
Lets think on the package names a bit. I set up a google group for us. I tried adding the svn commit messages to the group but I'm not sure that's possible. Maybe we just add each commiter manually as we go? Sean On 8/3/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 8/3/06, Sean Schofield [EMAIL PROTECTED] wrote: Any reason why we can't use org.apache.shale for the package names still? I can't really think of a better package name off hand. Using org.apache.shale.x would seem to create a false perception that the goodies were actually a formal part of the Shale project, and would contradict the project description claim in that regard. We should use goodies or shalegoodies or something like that. Sean Craig On 8/3/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 8/3/06, Sean Schofield [EMAIL PROTECTED] wrote: I'm ok with shale-goodies as long as we can release artifacts as different versions, etc. I'm assuming that's the case. I think we're all curious about the google option so lets go ahead with it. We can always move it in a few months if it doesn't pan out. Right now there;s just shale-petstore and it wouldn't be the end of the world to lose the svn history if we had to move it. I set up a maven/trunk/master-pom analogous to what we have in the Apache repository ... you could set up shale-petstore/trunk to make it independently branchable and so on. We could even set up a current externals later. We'll have to think about the package names (and Maven artifact ids) here ... I used shale-goodies:shale-goodies:1-SNAPSHOT for the initial master pom, but haven't checked in any code yet. my gmail is sean.schofield Added. Sean ps. Google is also doing something cool which is allowing you to host your domain email through them. There is a beta test going on and they accepted my application. Something to consider for folks who have their own domain for business purposes. That is pretty cool. Craig
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
On 8/3/06, Sean Schofield [EMAIL PROTECTED] wrote: Lets think on the package names a bit. OK. I set up a google group for us. I tried adding the svn commit messages to the group but I'm not sure that's possible. Maybe we just add each commiter manually as we go? Hmm ... looks like you have it set up right ... maybe commit mail isn't working yet. It also looks like we can only have one destination address for the commits. Sean Craig On 8/3/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 8/3/06, Sean Schofield [EMAIL PROTECTED] wrote: Any reason why we can't use org.apache.shale for the package names still? I can't really think of a better package name off hand. Using org.apache.shale.x would seem to create a false perception that the goodies were actually a formal part of the Shale project, and would contradict the project description claim in that regard. We should use goodies or shalegoodies or something like that. Sean Craig On 8/3/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 8/3/06, Sean Schofield [EMAIL PROTECTED] wrote: I'm ok with shale-goodies as long as we can release artifacts as different versions, etc. I'm assuming that's the case. I think we're all curious about the google option so lets go ahead with it. We can always move it in a few months if it doesn't pan out. Right now there;s just shale-petstore and it wouldn't be the end of the world to lose the svn history if we had to move it. I set up a maven/trunk/master-pom analogous to what we have in the Apache repository ... you could set up shale-petstore/trunk to make it independently branchable and so on. We could even set up a current externals later. We'll have to think about the package names (and Maven artifact ids) here ... I used shale-goodies:shale-goodies:1-SNAPSHOT for the initial master pom, but haven't checked in any code yet. my gmail is sean.schofield Added. Sean ps. Google is also doing something cool which is allowing you to host your domain email through them. There is a beta test going on and they accepted my application. Something to consider for folks who have their own domain for business purposes. That is pretty cool. Craig
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
Well the email list is not public atm. That's probably the problem. We could create a shell gmail account for the svn emails and have that same account subscribed to the group. Then set up forwarding. That should work. Which brings us to the issue of the list permissions. One option is to require the moderator approval to join the list (I believe that's what its set to now.) We could rubber stamp people who want to join but also remove them if they're acting like assholes. Or just let the floodgates open. The problem with the open flood gate approach is that it would be hard to switch back to the other model if we changed our mind. I'm not sure where I stand on this. What does the rest of the group think? Sean On 8/3/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 8/3/06, Sean Schofield [EMAIL PROTECTED] wrote: Lets think on the package names a bit. OK. I set up a google group for us. I tried adding the svn commit messages to the group but I'm not sure that's possible. Maybe we just add each commiter manually as we go? Hmm ... looks like you have it set up right ... maybe commit mail isn't working yet. It also looks like we can only have one destination address for the commits. Sean Craig On 8/3/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 8/3/06, Sean Schofield [EMAIL PROTECTED] wrote: Any reason why we can't use org.apache.shale for the package names still? I can't really think of a better package name off hand. Using org.apache.shale.x would seem to create a false perception that the goodies were actually a formal part of the Shale project, and would contradict the project description claim in that regard. We should use goodies or shalegoodies or something like that. Sean Craig On 8/3/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 8/3/06, Sean Schofield [EMAIL PROTECTED] wrote: I'm ok with shale-goodies as long as we can release artifacts as different versions, etc. I'm assuming that's the case. I think we're all curious about the google option so lets go ahead with it. We can always move it in a few months if it doesn't pan out. Right now there;s just shale-petstore and it wouldn't be the end of the world to lose the svn history if we had to move it. I set up a maven/trunk/master-pom analogous to what we have in the Apache repository ... you could set up shale-petstore/trunk to make it independently branchable and so on. We could even set up a current externals later. We'll have to think about the package names (and Maven artifact ids) here ... I used shale-goodies:shale-goodies:1-SNAPSHOT for the initial master pom, but haven't checked in any code yet. my gmail is sean.schofield Added. Sean ps. Google is also doing something cool which is allowing you to host your domain email through them. There is a beta test going on and they accepted my application. Something to consider for folks who have their own domain for business purposes. That is pretty cool. Craig
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
gmail mwessendorf @ gmail DOT com :) On 8/3/06, Sean Schofield [EMAIL PROTECTED] wrote: Well the email list is not public atm. That's probably the problem. We could create a shell gmail account for the svn emails and have that same account subscribed to the group. Then set up forwarding. That should work. Which brings us to the issue of the list permissions. One option is to require the moderator approval to join the list (I believe that's what its set to now.) We could rubber stamp people who want to join but also remove them if they're acting like assholes. Or just let the floodgates open. The problem with the open flood gate approach is that it would be hard to switch back to the other model if we changed our mind. I'm not sure where I stand on this. What does the rest of the group think? Sean On 8/3/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 8/3/06, Sean Schofield [EMAIL PROTECTED] wrote: Lets think on the package names a bit. OK. I set up a google group for us. I tried adding the svn commit messages to the group but I'm not sure that's possible. Maybe we just add each commiter manually as we go? Hmm ... looks like you have it set up right ... maybe commit mail isn't working yet. It also looks like we can only have one destination address for the commits. Sean Craig On 8/3/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 8/3/06, Sean Schofield [EMAIL PROTECTED] wrote: Any reason why we can't use org.apache.shale for the package names still? I can't really think of a better package name off hand. Using org.apache.shale.x would seem to create a false perception that the goodies were actually a formal part of the Shale project, and would contradict the project description claim in that regard. We should use goodies or shalegoodies or something like that. Sean Craig On 8/3/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 8/3/06, Sean Schofield [EMAIL PROTECTED] wrote: I'm ok with shale-goodies as long as we can release artifacts as different versions, etc. I'm assuming that's the case. I think we're all curious about the google option so lets go ahead with it. We can always move it in a few months if it doesn't pan out. Right now there;s just shale-petstore and it wouldn't be the end of the world to lose the svn history if we had to move it. I set up a maven/trunk/master-pom analogous to what we have in the Apache repository ... you could set up shale-petstore/trunk to make it independently branchable and so on. We could even set up a current externals later. We'll have to think about the package names (and Maven artifact ids) here ... I used shale-goodies:shale-goodies:1-SNAPSHOT for the initial master pom, but haven't checked in any code yet. my gmail is sean.schofield Added. Sean ps. Google is also doing something cool which is allowing you to host your domain email through them. There is a beta test going on and they accepted my application. Something to consider for folks who have their own domain for business purposes. That is pretty cool. Craig -- Matthias Wessendorf further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
Re: Should we move shale-petstore somewhere else? Was -- Re: Wikipedia: More Licensing Questions
Added. Craig On 8/3/06, Matthias Wessendorf [EMAIL PROTECTED] wrote: gmail mwessendorf @ gmail DOT com :) On 8/3/06, Sean Schofield [EMAIL PROTECTED] wrote: Well the email list is not public atm. That's probably the problem. We could create a shell gmail account for the svn emails and have that same account subscribed to the group. Then set up forwarding. That should work. Which brings us to the issue of the list permissions. One option is to require the moderator approval to join the list (I believe that's what its set to now.) We could rubber stamp people who want to join but also remove them if they're acting like assholes. Or just let the floodgates open. The problem with the open flood gate approach is that it would be hard to switch back to the other model if we changed our mind. I'm not sure where I stand on this. What does the rest of the group think? Sean On 8/3/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 8/3/06, Sean Schofield [EMAIL PROTECTED] wrote: Lets think on the package names a bit. OK. I set up a google group for us. I tried adding the svn commit messages to the group but I'm not sure that's possible. Maybe we just add each commiter manually as we go? Hmm ... looks like you have it set up right ... maybe commit mail isn't working yet. It also looks like we can only have one destination address for the commits. Sean Craig On 8/3/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 8/3/06, Sean Schofield [EMAIL PROTECTED] wrote: Any reason why we can't use org.apache.shale for the package names still? I can't really think of a better package name off hand. Using org.apache.shale.x would seem to create a false perception that the goodies were actually a formal part of the Shale project, and would contradict the project description claim in that regard. We should use goodies or shalegoodies or something like that. Sean Craig On 8/3/06, Craig McClanahan [EMAIL PROTECTED] wrote: On 8/3/06, Sean Schofield [EMAIL PROTECTED] wrote: I'm ok with shale-goodies as long as we can release artifacts as different versions, etc. I'm assuming that's the case. I think we're all curious about the google option so lets go ahead with it. We can always move it in a few months if it doesn't pan out. Right now there;s just shale-petstore and it wouldn't be the end of the world to lose the svn history if we had to move it. I set up a maven/trunk/master-pom analogous to what we have in the Apache repository ... you could set up shale-petstore/trunk to make it independently branchable and so on. We could even set up a current externals later. We'll have to think about the package names (and Maven artifact ids) here ... I used shale-goodies:shale-goodies:1-SNAPSHOT for the initial master pom, but haven't checked in any code yet. my gmail is sean.schofield Added. Sean ps. Google is also doing something cool which is allowing you to host your domain email through them. There is a beta test going on and they accepted my application. Something to consider for folks who have their own domain for business purposes. That is pretty cool. Craig -- Matthias Wessendorf further stuff: blog: http://jroller.com/page/mwessendorf mail: mwessendorf-at-gmail-dot-com
