January 2009 - implementations-list

[implementations-list] Transferring maintainership of Vimpulse (was: Re: viper-in-more-modes)
by Jason Spiro 29 Jan '09

29 Jan '09

2007/9/18, Stephen Bach <sjbach(a)comcast.net> wrote: > Sure, I'd be willing to put in a little effort. I'm currently running > Emacs 22 and a 23 snapshot. Let me know what I can do. Hi Stephen, Are you interested in taking over maintainership of Vimpulse? But sadly all the pending patches are just sitting in my inbox. Maybe I can forward them all to you? Or, if I don't manage to do that, I can give you my email login and password and you can dig them all up - just do a search through my email for "vimpulse" and maybe "viper-in-more-modes". An even more important problem: I think Vimpulse should be part of Emacs, so we should start getting copyright assignments now, or get all the code of Vimpulse released to the public domain by its authors. If you would like that, phone me day or evening at 416-992-3445 (I am on Eastern Standard Time) and I will give you the password. If you are no longer interested, I will seek another new maintainer. I will write an ad seeking a new maintainer inside the Vimpulse source code. BTW, dear list: Anyone interested? Cheers, -Jason

3 5

[implementations-list] Re: [gnu.org #393190] Dear FSF clerk, here are all my questions about copyright assigment
by Jason Spiro 29 Jan '09

29 Jan '09

On Mon, Jan 26, 2009 at 2:43 PM, Donald R Robertson III via RT <copyright-clerk(a)fsf.org> wrote: ... > In any > event, even if all the contributors place their work in the public > domain, we would still need at least a disclaimer from each of them if > the project were to become a part of emacs. So I'm not sure how much > time it would actually save to have them do that instead of just > assigning their work when the time comes. Thanks again for your > interest, and good luck with your project. Thanks Mr. Robertson. But when the time comes: 1. What if I can no longer reach them? 2. What if they then no longer want to bother with copyright assignment? I suspect it'd be very hard to then remove their code from Vimpulse. Are there any other options? For example, can you contact all contributors and ask them to assign copyright now, even though it's not strictly needed yet? Or can you send me a PDF of the FSF copyright assignment contract? I could then get every contributor to sign it and fax it to me when I merge their code. Then, when the time comes, I will fax my pile of contracts to you. When you reply to this email, please click the "Reply to All" button so that your reply will go to the whole Vimpulse mailing list will get your reply. Otherwise, I plan to forward all your future replies to the mailing list manually. If this is not ok, just let me know.

1 0

[implementations-list] Fwd: [gnu.org #393190] Dear FSF clerk, here are all my questions about copyright assigment
by Jason Spiro 27 Jan '09

27 Jan '09

---------- Forwarded message ---------- From: Donald R Robertson III via RT <copyright-clerk(a)fsf.org> Date: Mon, Jan 26, 2009 at 2:43 PM Subject: [gnu.org #393190] Dear FSF clerk, here are all my questions about copyright assigment To: jasonspiro3(a)gmail.com Hello, Thanks again for your interest. Sorry about the delay, your previous reply some how slipped past me. I can't really recommend any particular course of action in how to put your work in the public domain. In any event, even if all the contributors place their work in the public domain, we would still need at least a disclaimer from each of them if the project were to become a part of emacs. So I'm not sure how much time it would actually save to have them do that instead of just assigning their work when the time comes. Thanks again for your interest, and good luck with your project. > [jasonspiro3(a)gmail.com - Sun Jan 25 13:44:44 2009]: > > Hi Mr. Robertson, > > I still didn't get a reply yet, so I am resending my message to you. > > Hi Mr. Robertson, > > No, I have not applied to get either of the two works into Emacs yet. > I and others agree it that Vimpulse is too buggy to get into Emacs > yet. And I don't care enough about viper-in-more-modes to try to get > it into Emacs. But I want to make sure the projects can easily get > into Emacs when needed. So I think I will get all the contributors to > release their contributions to the public domain. I will probably do > so by asking them to go through the clickthrough public domain > dedication process at > http://creativecommons.org/license/publicdomain-2 and then forward the > email receipt they get to the bug tracker. Do you think that is a > good and safe method for people to dedicate work to the public domain, > that will work no matter what country they come from (e.g. Canada, > Italy, China)? > > If you reply, please make sure to Reply to All. > > -Jason

1 0

[implementations-list] 2nd send: Re: [gnu.org #393190] Dear FSF clerk, here are all my questions about copyright assigment
by Jason Spiro 25 Jan '09

25 Jan '09

Hi Mr. Robertson, I still didn't get a reply yet, so I am resending my message to you. 2008/12/1 Donald R Robertson III via RT <copyright-clerk(a)fsf.org> wrote: > Hello, > > It is great to hear that you are interested in contributing to Emacs. > There's actually a bit of process for getting your work included in > Emacs that I'm not sure you have gone through yet. If you have, I > apologize. You should go to https://savannah.gnu.org, if you are not > already a member there, then sign up and login. Then go to the Emacs > page, then click on the members list. There is a link there to a form > for requesting inclusion on the project. We won't need to have an > assignment on file until you go through this process and have your work > included. > > Putting your work in the public domain is okay, as such work can be > included in the GNU Project. The only issue really is that proprietary > developers can use your work if it is in the public domain. > > As for the rest of your questions, I think we should just hold off on > them until we know that the work is going to be included. It's better to > have someone take a look at a work before determining whether an > assignment is needed, and that takes a bit of time to do. If the work is > not included in Emacs, then we can about other options you might use to > get your work distributed freely. > > Thanks again for your interest in contributing, and good luck. > -- > Sincerely, > > Donald R. Robertson, III, J.D. > Assignment Administrator > Free Software Foundation > 51 Franklin Street, Fifth Floor > Boston, MA 02110 > Phone +1-617-542-5942 > Fax +1-617-542-2652 Hi Mr. Robertson, No, I have not applied to get either of the two works into Emacs yet. I and others agree it that Vimpulse is too buggy to get into Emacs yet. And I don't care enough about viper-in-more-modes to try to get it into Emacs. But I want to make sure the projects can easily get into Emacs when needed. So I think I will get all the contributors to release their contributions to the public domain. I will probably do so by asking them to go through the clickthrough public domain dedication process at http://creativecommons.org/license/publicdomain-2 and then forward the email receipt they get to the bug tracker. Do you think that is a good and safe method for people to dedicate work to the public domain, that will work no matter what country they come from (e.g. Canada, Italy, China)? If you reply, please make sure to Reply to All. -Jason

1 0