On Mon, 2008-05-19 at 15:29 -0700, tim Rowledge wrote:
I'd like to ask the box-admins to make a few changes to the Mantis setup in aid of making sure we are totally clear on the licensing of future contributions. Not being any sort of expert in Mantis setup, I may well be asking for something impossible, in which case I'm sure I will be told about it.
On the main page, we need a clear announcement that any code contributed as a bugfix MUST be MIT license and that submitting code in a Mantis report is taken as explicit notification that the code is so licensed. Personally, I'd say that we should take this position for *any* code but possibly some people may have valid arguments that it is not appropriate for certain packages or projects. If is plausible to allow for this, then we should consider it.
First we need to define 'main page'. This actually is determined by whether you are logged in or not and what project you were last looking at. Were you thinking of the page that currently has the notice regarding adding the report number to the filename of any attachments? This page is specific to the Squeak project. I can easily add a notice to this page and in fact I think it is appropriate that it be on this page which will only be seen if Squeak is the selected project. I think any notice, if any, we put on the Squeak Packages project will need to be different.
Should I just write up my own notice or would you like to provide specific text?
On the 'Report Issue' page I suggest that we have a repeat of the main page note.
Where do you see a note going on the report page?
If possible some sort of pop-up notification when uploading a file (a fairly typical action when submitting a proposed solution) might be sensible.
When would such a pop-up notification be triggered? On hitting the 'Upload File' button?
I would suggest having a short form of the notice on all pages either in the footer or perhaps header which is consistently displayed on all pages.
Note that we could probably hash this out much quicker on IRC or a Skype chat.
Ken
tim
tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Porting is such sweet sorrow
On 20-May-08, at 1:23 PM, Ken Causey wrote:
First we need to define 'main page'. This actually is determined by whether you are logged in or not and what project you were last looking at. Were you thinking of the page that currently has the notice regarding adding the report number to the filename of any attachments? This page is specific to the Squeak project. I can easily add a notice to this page and in fact I think it is appropriate that it be on this page which will only be seen if Squeak is the selected project. I think any notice, if any, we put on the Squeak Packages project will need to be different.
Sounds sensible to me; I was indeed thinking of the page you mention and I agree that different rules may well apply to core and packages.
Should I just write up my own notice or would you like to provide specific text?
Hmm, I guess we should discuss this at tomorrow's board meeting and let you know. Suggestions from the wider community are welcome of course.
I'll start the ball rolling with "Hey You! Read this NOW. Any code submitted to this Mantis system as a fix or suggested fix for the Squeak core system must be offered under the terms of the MIT license <-link. Code entered here in the Description, Additional Information or Notes, or uploaded as a file, is assumed to be so licensed"
On the 'Report Issue' page I suggest that we have a repeat of the main page note.
Where do you see a note going on the report page?
If it's possible, right near the top - around where it says 'Enter Report Details'. In letters of eldrich fire that burn into your retinas. In a non-violent, harmless, non-judgemental manner, of course.
If possible some sort of pop-up notification when uploading a file (a fairly typical action when submitting a proposed solution) might be sensible.
When would such a pop-up notification be triggered? On hitting the 'Upload File' button?
Yes. It may be going Too Far(tm) but at least we should consider it as an option.
I would suggest having a short form of the notice on all pages either in the footer or perhaps header which is consistently displayed on all pages.
Excellent idea. Maybe a really short form like "You need to be aware of the licensing rules for this project" with a link built in.
Note that we could probably hash this out much quicker on IRC or a Skype chat.
Probably true. We may try to add you to the board meeting skype tomorrow if that is ok.
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Strange OpCodes: L: Lie!
On Tue, 2008-05-20 at 17:25 -0700, tim Rowledge wrote:
On 20-May-08, at 1:23 PM, Ken Causey wrote:
Should I just write up my own notice or would you like to provide specific text?
Hmm, I guess we should discuss this at tomorrow's board meeting and let you know. Suggestions from the wider community are welcome of course.
I'll start the ball rolling with "Hey You! Read this NOW. Any code submitted to this Mantis system as a fix or suggested fix for the Squeak core system must be offered under the terms of the MIT license <-link. Code entered here in the Description, Additional Information or Notes, or uploaded as a file, is assumed to be so licensed"
If the Board would like me to, I could attend. But I think it is probably sufficient if the everyone on the Board has an opportunity to give any opinions on the issue, as already discussed via email, and then continue to delegate to you. I suspect that between the two of us (you can bring the 'crazy' and I will bring the 'boring') we can hash it out.
I'm not sure of the desired schedule on this but I would like to request the opportunity to upgrade both PHP and Mantis on the server before doing this. One of the problems with doing something like this is having to maintain it as we upgrade Mantis. For that reason I would prefer to do the upgrade prior to the changes. And for that matter I have at least a change or two I will already have to port.
Given that I want to also go ahead and upgrade PHP as well I would like some time to do some testing and would request about a two week schedule on completing the upgrades and adding the first version of license notification support.
Ken
Actually, I should clarify: Adding the notice to the 'front page' is easy, requiring no source code changes, so can be done immediately. It is the other changes that are more involved and that I would like some time to complete.
Ken
On Wed, 2008-05-21 at 11:03 -0500, Ken Causey wrote:
On Tue, 2008-05-20 at 17:25 -0700, tim Rowledge wrote:
On 20-May-08, at 1:23 PM, Ken Causey wrote:
Should I just write up my own notice or would you like to provide specific text?
Hmm, I guess we should discuss this at tomorrow's board meeting and let you know. Suggestions from the wider community are welcome of course.
I'll start the ball rolling with "Hey You! Read this NOW. Any code submitted to this Mantis system as a fix or suggested fix for the Squeak core system must be offered under the terms of the MIT license <-link. Code entered here in the Description, Additional Information or Notes, or uploaded as a file, is assumed to be so licensed"
If the Board would like me to, I could attend. But I think it is probably sufficient if the everyone on the Board has an opportunity to give any opinions on the issue, as already discussed via email, and then continue to delegate to you. I suspect that between the two of us (you can bring the 'crazy' and I will bring the 'boring') we can hash it out.
I'm not sure of the desired schedule on this but I would like to request the opportunity to upgrade both PHP and Mantis on the server before doing this. One of the problems with doing something like this is having to maintain it as we upgrade Mantis. For that reason I would prefer to do the upgrade prior to the changes. And for that matter I have at least a change or two I will already have to port.
Given that I want to also go ahead and upgrade PHP as well I would like some time to do some testing and would request about a two week schedule on completing the upgrades and adding the first version of license notification support.
Ken
box-admins@lists.squeakfoundation.org
-
Ken Causey -
tim Rowledge