Re: Openmeetings - A Shepherd's View
Thx Mohammad! We would have some more releases ready if the legal status of the plugins is clear. I hope we can resolve it soon. Sebastian 2012/9/18 Mohammad Nour El-Din nour.moham...@gmail.com: Hi... From all the replies we got so far I don't see any legal concerns and hence I take my question/concern back. In either way, keep the good work OpenMeetings ;) On Mon, Sep 17, 2012 at 10:52 PM, dsh daniel.hais...@gmail.com wrote: Well I still opt to use Meta descriptors such as Maven POMs or CMake (probably only applicable for native projects) files in such cases which would allow to generate Eclipse/IDE you name it specific files once the sources has been obtained. Cheers Daniel On Mon, Sep 17, 2012 at 10:22 PM, sebb seb...@gmail.com wrote: On 14 September 2012 13:57, Alexei Fedotov alexei.fedo...@gmail.com wrote: The most useful file containing the project classpath is only formatted automatically, it cannot be generated without project-specific knowledge. There is no techical problem to drop these files, yet developers who download our source release loose a useful code navigation tool without these files. Unfortunately, Eclipse .classpath and .project files are *not* portable; the contents can depend on the individual Eclipse setup. In particular, unless all developers use the same default JDK as required by the project, the classpath files will vary. Also, the .project file will vary if some developers have added certain plugins, e.g. FindBugs or Maven. Having the files in SVN in the location where Eclipse expects to find them will cause problems for some developers, as they will need to modify the files locally in order to build. They cannot commit the files without causing problems for others, and so their workspace will always contain modifications. If you do wish to release IDE build files, I suggest you release them as separate files, e.g. under res/ide-support/eclipse res/ide-support/netbeans etc. The files can be named eclipse.classpath eclipse.profile as files without names can cause problems. 14.09.2012 16:46 пользователь Jim Jagielski j...@jagunet.com написал: On Sep 14, 2012, at 5:02 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: But can we add ASL headers to files which are defined and considered to be, even structure wise (please correct me if I am wrong), under the license of Eclipse ? If they are build artifacts (like stuff created by autoconf for example), then there's no need to add AL headers (AL, not ASL). AL headers are for actual work products (like source code, etc)... - 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 -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com seba.wag...@gmail.com - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Openmeetings - A Shepherd's View
Hi... From all the replies we got so far I don't see any legal concerns and hence I take my question/concern back. In either way, keep the good work OpenMeetings ;) On Mon, Sep 17, 2012 at 10:52 PM, dsh daniel.hais...@gmail.com wrote: Well I still opt to use Meta descriptors such as Maven POMs or CMake (probably only applicable for native projects) files in such cases which would allow to generate Eclipse/IDE you name it specific files once the sources has been obtained. Cheers Daniel On Mon, Sep 17, 2012 at 10:22 PM, sebb seb...@gmail.com wrote: On 14 September 2012 13:57, Alexei Fedotov alexei.fedo...@gmail.com wrote: The most useful file containing the project classpath is only formatted automatically, it cannot be generated without project-specific knowledge. There is no techical problem to drop these files, yet developers who download our source release loose a useful code navigation tool without these files. Unfortunately, Eclipse .classpath and .project files are *not* portable; the contents can depend on the individual Eclipse setup. In particular, unless all developers use the same default JDK as required by the project, the classpath files will vary. Also, the .project file will vary if some developers have added certain plugins, e.g. FindBugs or Maven. Having the files in SVN in the location where Eclipse expects to find them will cause problems for some developers, as they will need to modify the files locally in order to build. They cannot commit the files without causing problems for others, and so their workspace will always contain modifications. If you do wish to release IDE build files, I suggest you release them as separate files, e.g. under res/ide-support/eclipse res/ide-support/netbeans etc. The files can be named eclipse.classpath eclipse.profile as files without names can cause problems. 14.09.2012 16:46 пользователь Jim Jagielski j...@jagunet.com написал: On Sep 14, 2012, at 5:02 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: But can we add ASL headers to files which are defined and considered to be, even structure wise (please correct me if I am wrong), under the license of Eclipse ? If they are build artifacts (like stuff created by autoconf for example), then there's no need to add AL headers (AL, not ASL). AL headers are for actual work products (like source code, etc)... - 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 -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Openmeetings - A Shepherd's View
On 14 September 2012 13:57, Alexei Fedotov alexei.fedo...@gmail.com wrote: The most useful file containing the project classpath is only formatted automatically, it cannot be generated without project-specific knowledge. There is no techical problem to drop these files, yet developers who download our source release loose a useful code navigation tool without these files. Unfortunately, Eclipse .classpath and .project files are *not* portable; the contents can depend on the individual Eclipse setup. In particular, unless all developers use the same default JDK as required by the project, the classpath files will vary. Also, the .project file will vary if some developers have added certain plugins, e.g. FindBugs or Maven. Having the files in SVN in the location where Eclipse expects to find them will cause problems for some developers, as they will need to modify the files locally in order to build. They cannot commit the files without causing problems for others, and so their workspace will always contain modifications. If you do wish to release IDE build files, I suggest you release them as separate files, e.g. under res/ide-support/eclipse res/ide-support/netbeans etc. The files can be named eclipse.classpath eclipse.profile as files without names can cause problems. 14.09.2012 16:46 пользователь Jim Jagielski j...@jagunet.com написал: On Sep 14, 2012, at 5:02 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: But can we add ASL headers to files which are defined and considered to be, even structure wise (please correct me if I am wrong), under the license of Eclipse ? If they are build artifacts (like stuff created by autoconf for example), then there's no need to add AL headers (AL, not ASL). AL headers are for actual work products (like source code, etc)... - 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: Openmeetings - A Shepherd's View
On 14 September 2012 17:53, Benson Margulies bimargul...@gmail.com wrote: Does anyone seriously believe that IP notices are required in files like these? These files cannot be copyrighted because they do not have any 'creative' content. If they can't be copyrighted, they can't be licensed. And, even it were otherwise, the notices at the top of the tree are sufficient. This isn't the first instance of a 'source' file format that has no provisions for an IP notice. Just for completeness: the file format does allow comments; it is standard XML and can therefore contain an IP notice should one be required. On Fri, Sep 14, 2012 at 9:42 AM, dsh daniel.hais...@gmail.com wrote: Well I think Maven allows to create both Eclipse and IDEA IntelliJ projects including metdata artifacts such as .classpath files... Cheers Daniel On Fri, Sep 14, 2012 at 2:57 PM, Alexei Fedotov alexei.fedo...@gmail.com wrote: The most useful file containing the project classpath is only formatted automatically, it cannot be generated without project-specific knowledge. There is no techical problem to drop these files, yet developers who download our source release loose a useful code navigation tool without these files. 14.09.2012 16:46 пользователь Jim Jagielski j...@jagunet.com написал: On Sep 14, 2012, at 5:02 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: But can we add ASL headers to files which are defined and considered to be, even structure wise (please correct me if I am wrong), under the license of Eclipse ? If they are build artifacts (like stuff created by autoconf for example), then there's no need to add AL headers (AL, not ASL). AL headers are for actual work products (like source code, etc)... - 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: Openmeetings - A Shepherd's View
Well I still opt to use Meta descriptors such as Maven POMs or CMake (probably only applicable for native projects) files in such cases which would allow to generate Eclipse/IDE you name it specific files once the sources has been obtained. Cheers Daniel On Mon, Sep 17, 2012 at 10:22 PM, sebb seb...@gmail.com wrote: On 14 September 2012 13:57, Alexei Fedotov alexei.fedo...@gmail.com wrote: The most useful file containing the project classpath is only formatted automatically, it cannot be generated without project-specific knowledge. There is no techical problem to drop these files, yet developers who download our source release loose a useful code navigation tool without these files. Unfortunately, Eclipse .classpath and .project files are *not* portable; the contents can depend on the individual Eclipse setup. In particular, unless all developers use the same default JDK as required by the project, the classpath files will vary. Also, the .project file will vary if some developers have added certain plugins, e.g. FindBugs or Maven. Having the files in SVN in the location where Eclipse expects to find them will cause problems for some developers, as they will need to modify the files locally in order to build. They cannot commit the files without causing problems for others, and so their workspace will always contain modifications. If you do wish to release IDE build files, I suggest you release them as separate files, e.g. under res/ide-support/eclipse res/ide-support/netbeans etc. The files can be named eclipse.classpath eclipse.profile as files without names can cause problems. 14.09.2012 16:46 пользователь Jim Jagielski j...@jagunet.com написал: On Sep 14, 2012, at 5:02 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: But can we add ASL headers to files which are defined and considered to be, even structure wise (please correct me if I am wrong), under the license of Eclipse ? If they are build artifacts (like stuff created by autoconf for example), then there's no need to add AL headers (AL, not ASL). AL headers are for actual work products (like source code, etc)... - 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: Openmeetings - A Shepherd's View
Hi Alexei... On Fri, Sep 14, 2012 at 4:24 AM, Alexei Fedotov alexei.fedo...@gmail.com wrote: Hello Mohammad, thank you for the review. Eclipse can be considered as an alternative build system, so these files are like build.xml files. Why not to keep them in release? 14.09.2012 3:46 пользователь Mohammad Nour El-Din mn...@apache.org написал: Hi I checked: - Mailing lists and from it the community looks active to a good extent both on the users and developers lists - Last report (June 2012) they were in the 'No Release' group of podlings but they managed to get a release out - Their progress is not that fast but it is stable and steady One minor note: - In [1] I noticed files related to Eclipse like .classpath and .project, I am not sure that these files should be in a release tag. Comments about that ? Well my concern was more like a question to raise here not actually something to take on the project itself, to be honest I am not aware about any rules that might prohibit that, but for at least most of the projects I didn't see them committing IDE specific files into the repository. Thats why I raised the question here to see what others do. [1] https://svn.apache.org/repos/asf/incubator/openmeetings/tags/2.0/ -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Openmeetings - A Shepherd's View
On Sep 14, 2012, at 10:24 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: On Fri, Sep 14, 2012 at 4:24 AM, Alexei Fedotov alexei.fedo...@gmail.com wrote: 14.09.2012 3:46 пользователь Mohammad Nour El-Din mn...@apache.org написал: One minor note: - In [1] I noticed files related to Eclipse like .classpath and .project, I am not sure that these files should be in a release tag. Comments about that ? Well my concern was more like a question to raise here not actually something to take on the project itself, to be honest I am not aware about any rules that might prohibit that, but for at least most of the projects I didn't see them committing IDE specific files into the repository. Thats why I raised the question here to see what others do. Since these are xml files and you can definitely edit them like other build files, I can't see any reason why they could not be part of a source release either. However, I do think they need a proper license header (the file I quickly checked [1] did not have that). I'm not aware of a way to tell Eclipse to add such headers automatically, so you might have to do that by hand or some script. Greetings, Marcel [1] https://svn.apache.org/repos/asf/incubator/openmeetings/tags/2.0/.project
Re: Openmeetings - A Shepherd's View
Hi Marcel... On Fri, Sep 14, 2012 at 10:40 AM, Marcel Offermans marcel.offerm...@luminis.nl wrote: On Sep 14, 2012, at 10:24 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: On Fri, Sep 14, 2012 at 4:24 AM, Alexei Fedotov alexei.fedo...@gmail.com wrote: 14.09.2012 3:46 пользователь Mohammad Nour El-Din mn...@apache.org написал: One minor note: - In [1] I noticed files related to Eclipse like .classpath and .project, I am not sure that these files should be in a release tag. Comments about that ? Well my concern was more like a question to raise here not actually something to take on the project itself, to be honest I am not aware about any rules that might prohibit that, but for at least most of the projects I didn't see them committing IDE specific files into the repository. Thats why I raised the question here to see what others do. Since these are xml files and you can definitely edit them like other build files, I can't see any reason why they could not be part of a source release either. However, I do think they need a proper license header (the file I quickly checked [1] did not have that). I'm not aware of a way to tell Eclipse to add such headers automatically, so you might have to do that by hand or some script. But can we add ASL headers to files which are defined and considered to be, even structure wise (please correct me if I am wrong), under the license of Eclipse ? I really don't know I am also just raising a question here DETAILS: My concern here comes from information I learned when I was working in a big company (not mentioning names here) and they had their own development tools which are totally built based on Eclipse. And IIRC even the files generated from these tools, also XML files and such, were opt to some license some how. So IDK if the case hold here as well or not Greetings, Marcel [1] https://svn.apache.org/repos/asf/incubator/openmeetings/tags/2.0/.project -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Openmeetings - A Shepherd's View
@Mohammad: And btw, in reference to that big (blue) company, I'd say your statement is hearsay and needs to be proofed. For instance why is that very big (blue) company adding their own, proprietary license header to such generated files and in one way or another even Java files are Eclipse-generated in the beginning ;) Cheers Daniel On Fri, Sep 14, 2012 at 11:07 AM, dsh daniel.hais...@gmail.com wrote: The more practical and pragmatic question to pose is: why would you want to add license headers to generated files. You would have to take care of that they won't disappear each time the file (e.g. .classpath) is getting re-generated. Again from a practical point of view a mentoring suggestion could be to suggest moving such configuration settings over to Maven over the course of time and let Maven generate the Eclipse project-specific files. Cheers Daniel On Fri, Sep 14, 2012 at 11:02 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: Hi Marcel... On Fri, Sep 14, 2012 at 10:40 AM, Marcel Offermans marcel.offerm...@luminis.nl wrote: On Sep 14, 2012, at 10:24 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: On Fri, Sep 14, 2012 at 4:24 AM, Alexei Fedotov alexei.fedo...@gmail.com wrote: 14.09.2012 3:46 пользователь Mohammad Nour El-Din mn...@apache.org написал: One minor note: - In [1] I noticed files related to Eclipse like .classpath and .project, I am not sure that these files should be in a release tag. Comments about that ? Well my concern was more like a question to raise here not actually something to take on the project itself, to be honest I am not aware about any rules that might prohibit that, but for at least most of the projects I didn't see them committing IDE specific files into the repository. Thats why I raised the question here to see what others do. Since these are xml files and you can definitely edit them like other build files, I can't see any reason why they could not be part of a source release either. However, I do think they need a proper license header (the file I quickly checked [1] did not have that). I'm not aware of a way to tell Eclipse to add such headers automatically, so you might have to do that by hand or some script. But can we add ASL headers to files which are defined and considered to be, even structure wise (please correct me if I am wrong), under the license of Eclipse ? I really don't know I am also just raising a question here DETAILS: My concern here comes from information I learned when I was working in a big company (not mentioning names here) and they had their own development tools which are totally built based on Eclipse. And IIRC even the files generated from these tools, also XML files and such, were opt to some license some how. So IDK if the case hold here as well or not Greetings, Marcel [1] https://svn.apache.org/repos/asf/incubator/openmeetings/tags/2.0/.project -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - 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: Openmeetings - A Shepherd's View
The more practical and pragmatic question to pose is: why would you want to add license headers to generated files. You would have to take care of that they won't disappear each time the file (e.g. .classpath) is getting re-generated. Again from a practical point of view a mentoring suggestion could be to suggest moving such configuration settings over to Maven over the course of time and let Maven generate the Eclipse project-specific files. Cheers Daniel On Fri, Sep 14, 2012 at 11:02 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: Hi Marcel... On Fri, Sep 14, 2012 at 10:40 AM, Marcel Offermans marcel.offerm...@luminis.nl wrote: On Sep 14, 2012, at 10:24 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: On Fri, Sep 14, 2012 at 4:24 AM, Alexei Fedotov alexei.fedo...@gmail.com wrote: 14.09.2012 3:46 пользователь Mohammad Nour El-Din mn...@apache.org написал: One minor note: - In [1] I noticed files related to Eclipse like .classpath and .project, I am not sure that these files should be in a release tag. Comments about that ? Well my concern was more like a question to raise here not actually something to take on the project itself, to be honest I am not aware about any rules that might prohibit that, but for at least most of the projects I didn't see them committing IDE specific files into the repository. Thats why I raised the question here to see what others do. Since these are xml files and you can definitely edit them like other build files, I can't see any reason why they could not be part of a source release either. However, I do think they need a proper license header (the file I quickly checked [1] did not have that). I'm not aware of a way to tell Eclipse to add such headers automatically, so you might have to do that by hand or some script. But can we add ASL headers to files which are defined and considered to be, even structure wise (please correct me if I am wrong), under the license of Eclipse ? I really don't know I am also just raising a question here DETAILS: My concern here comes from information I learned when I was working in a big company (not mentioning names here) and they had their own development tools which are totally built based on Eclipse. And IIRC even the files generated from these tools, also XML files and such, were opt to some license some how. So IDK if the case hold here as well or not Greetings, Marcel [1] https://svn.apache.org/repos/asf/incubator/openmeetings/tags/2.0/.project -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - 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: Openmeetings - A Shepherd's View
Hi Daniel... On Fri, Sep 14, 2012 at 11:11 AM, dsh daniel.hais...@gmail.com wrote: @Mohammad: And btw, in reference to that big (blue) company, I'd say your statement is hearsay and needs to be proofed. For instance why is that very big (blue) company adding their own, proprietary license header to such generated files and in one way or another even Java files are Eclipse-generated in the beginning ;) To be honest I don't remember correctly cause that was since before 2008, but I remember vaguely that I wanted to do something and I was not allowed to because of some rules related to this big (blue) company :D, so I thought it is better to bring that up again maybe someone already know more details or an answer Cheers Daniel On Fri, Sep 14, 2012 at 11:07 AM, dsh daniel.hais...@gmail.com wrote: The more practical and pragmatic question to pose is: why would you want to add license headers to generated files. You would have to take care of that they won't disappear each time the file (e.g. .classpath) is getting re-generated. Again from a practical point of view a mentoring suggestion could be to suggest moving such configuration settings over to Maven over the course of time and let Maven generate the Eclipse project-specific files. Cheers Daniel On Fri, Sep 14, 2012 at 11:02 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: Hi Marcel... On Fri, Sep 14, 2012 at 10:40 AM, Marcel Offermans marcel.offerm...@luminis.nl wrote: On Sep 14, 2012, at 10:24 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: On Fri, Sep 14, 2012 at 4:24 AM, Alexei Fedotov alexei.fedo...@gmail.com wrote: 14.09.2012 3:46 пользователь Mohammad Nour El-Din mn...@apache.org написал: One minor note: - In [1] I noticed files related to Eclipse like .classpath and .project, I am not sure that these files should be in a release tag. Comments about that ? Well my concern was more like a question to raise here not actually something to take on the project itself, to be honest I am not aware about any rules that might prohibit that, but for at least most of the projects I didn't see them committing IDE specific files into the repository. Thats why I raised the question here to see what others do. Since these are xml files and you can definitely edit them like other build files, I can't see any reason why they could not be part of a source release either. However, I do think they need a proper license header (the file I quickly checked [1] did not have that). I'm not aware of a way to tell Eclipse to add such headers automatically, so you might have to do that by hand or some script. But can we add ASL headers to files which are defined and considered to be, even structure wise (please correct me if I am wrong), under the license of Eclipse ? I really don't know I am also just raising a question here DETAILS: My concern here comes from information I learned when I was working in a big company (not mentioning names here) and they had their own development tools which are totally built based on Eclipse. And IIRC even the files generated from these tools, also XML files and such, were opt to some license some how. So IDK if the case hold here as well or not Greetings, Marcel [1] https://svn.apache.org/repos/asf/incubator/openmeetings/tags/2.0/.project -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - 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 -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Openmeetings - A Shepherd's View
On Sep 14, 2012, at 5:02 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: But can we add ASL headers to files which are defined and considered to be, even structure wise (please correct me if I am wrong), under the license of Eclipse ? If they are build artifacts (like stuff created by autoconf for example), then there's no need to add AL headers (AL, not ASL). AL headers are for actual work products (like source code, etc)... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Openmeetings - A Shepherd's View
The most useful file containing the project classpath is only formatted automatically, it cannot be generated without project-specific knowledge. There is no techical problem to drop these files, yet developers who download our source release loose a useful code navigation tool without these files. 14.09.2012 16:46 пользователь Jim Jagielski j...@jagunet.com написал: On Sep 14, 2012, at 5:02 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: But can we add ASL headers to files which are defined and considered to be, even structure wise (please correct me if I am wrong), under the license of Eclipse ? If they are build artifacts (like stuff created by autoconf for example), then there's no need to add AL headers (AL, not ASL). AL headers are for actual work products (like source code, etc)... - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Openmeetings - A Shepherd's View
Does anyone seriously believe that IP notices are required in files like these? These files cannot be copyrighted because they do not have any 'creative' content. If they can't be copyrighted, they can't be licensed. And, even it were otherwise, the notices at the top of the tree are sufficient. This isn't the first instance of a 'source' file format that has no provisions for an IP notice. On Fri, Sep 14, 2012 at 9:42 AM, dsh daniel.hais...@gmail.com wrote: Well I think Maven allows to create both Eclipse and IDEA IntelliJ projects including metdata artifacts such as .classpath files... Cheers Daniel On Fri, Sep 14, 2012 at 2:57 PM, Alexei Fedotov alexei.fedo...@gmail.com wrote: The most useful file containing the project classpath is only formatted automatically, it cannot be generated without project-specific knowledge. There is no techical problem to drop these files, yet developers who download our source release loose a useful code navigation tool without these files. 14.09.2012 16:46 пользователь Jim Jagielski j...@jagunet.com написал: On Sep 14, 2012, at 5:02 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: But can we add ASL headers to files which are defined and considered to be, even structure wise (please correct me if I am wrong), under the license of Eclipse ? If they are build artifacts (like stuff created by autoconf for example), then there's no need to add AL headers (AL, not ASL). AL headers are for actual work products (like source code, etc)... - 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: Openmeetings - A Shepherd's View
Hi Benson... On Fri, Sep 14, 2012 at 6:53 PM, Benson Margulies bimargul...@gmail.com wrote: Does anyone seriously believe that IP notices are required in files like these? These files cannot be copyrighted because they do not have any 'creative' content. If they can't be copyrighted, they can't be licensed. And, even it were otherwise, the notices at the top of the tree are sufficient. This isn't the first instance of a 'source' file format that has no provisions for an IP notice. Thanks for the explanation. Then my question/concern is not valid and hence I take it back. On Fri, Sep 14, 2012 at 9:42 AM, dsh daniel.hais...@gmail.com wrote: Well I think Maven allows to create both Eclipse and IDEA IntelliJ projects including metdata artifacts such as .classpath files... Cheers Daniel On Fri, Sep 14, 2012 at 2:57 PM, Alexei Fedotov alexei.fedo...@gmail.com wrote: The most useful file containing the project classpath is only formatted automatically, it cannot be generated without project-specific knowledge. There is no techical problem to drop these files, yet developers who download our source release loose a useful code navigation tool without these files. 14.09.2012 16:46 пользователь Jim Jagielski j...@jagunet.com написал: On Sep 14, 2012, at 5:02 AM, Mohammad Nour El-Din nour.moham...@gmail.com wrote: But can we add ASL headers to files which are defined and considered to be, even structure wise (please correct me if I am wrong), under the license of Eclipse ? If they are build artifacts (like stuff created by autoconf for example), then there's no need to add AL headers (AL, not ASL). AL headers are for actual work products (like source code, etc)... - 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 -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Openmeetings - A Shepherd's View
Hi, On Fri, Sep 14, 2012 at 1:46 AM, Mohammad Nour El-Din mn...@apache.org wrote: I checked: - Mailing lists and from it the community looks active to a good extent both on the users and developers lists - Last report (June 2012) they were in the 'No Release' group of podlings but they managed to get a release out - Their progress is not that fast but it is stable and steady Great, thanks for the review! I notice that the only reason mentioned in the report for holding off graduation is not all code released. The Incubator is mostly concerned that you know how to cut Apache releases, and thus showing that ability (typically by cutting an actual release) is a graduation requirement, but there's no need for all the code to be released before graduation. Thus, and given that there don't seem to be any other obvious graduation issues, it looks to me like OpenMeetings should be ready to graduate as soon as they think it's time to do so. BR, Jukka Zitting - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Openmeetings - A Shepherd's View
Hi I checked: - Mailing lists and from it the community looks active to a good extent both on the users and developers lists - Last report (June 2012) they were in the 'No Release' group of podlings but they managed to get a release out - Their progress is not that fast but it is stable and steady One minor note: - In [1] I noticed files related to Eclipse like .classpath and .project, I am not sure that these files should be in a release tag. Comments about that ? [1] https://svn.apache.org/repos/asf/incubator/openmeetings/tags/2.0/ -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Openmeetings - A Shepherd's View
Hello Mohammad, thank you for the review. Eclipse can be considered as an alternative build system, so these files are like build.xml files. Why not to keep them in release? 14.09.2012 3:46 пользователь Mohammad Nour El-Din mn...@apache.org написал: Hi I checked: - Mailing lists and from it the community looks active to a good extent both on the users and developers lists - Last report (June 2012) they were in the 'No Release' group of podlings but they managed to get a release out - Their progress is not that fast but it is stable and steady One minor note: - In [1] I noticed files related to Eclipse like .classpath and .project, I am not sure that these files should be in a release tag. Comments about that ? [1] https://svn.apache.org/repos/asf/incubator/openmeetings/tags/2.0/ -- Thanks - Mohammad Nour Life is like riding a bicycle. To keep your balance you must keep moving - Albert Einstein - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
