-
-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add to GNU ELPA? #50
Comments
@syohex: if all these bugs are really fixed in company's popup lib, I think it's worth it to backport them to auto-complete's popup no? What is the showstopper? |
Sorry we have no plan to upload GNU ELPA. |
The advantage would be that Company would be able to use it. And any packages that use popup.el for visualization now would be possible to publish to GNU ELPA. |
@syohex: what about my question about the bugfixes? If it's fixed in some fork it ought to be backported here |
It's not a fork, it's a different package. |
Oh okay... but my point still stands. There is someone (you) volonteering to fix a lot of long standing bugs and if it was me maintaining popup I'd be like It's surprising. |
That still requires copyright assignment. And the chances of obtaining copyright papers from all contributors are even more slim now. |
I am curious on how are these copy assignment process? Sorry I don't have the experience on this. I think the first step would just need a list of contributors? 😕 |
Indeed. You can obtain such list from Git history. Or simply Then: https://www.gnu.org/software/emacs/manual/html_node/emacs/Copyright-Assignment.html |
|
This is the current result from command Log here.
Let's not talk about the non-trivial part yet. Here is the full list of all the contributors on the list including there contributions.
I guess we just need all people on the list to sign copyright assignments to FSF? 😅 EDIT: Just in case if you are confused why you are being notify by this thread, we are planning on pushing this package to elpa and we need all contributors to sign copyright assignments to FSF (See the link here). Let us know what you think! Thanks! 😄 |
I recommend that you look at the log on Github to easily match legal names to Github usernames. Once you have compiled the list you should post it here to invite these people to comment. I should not just update the above list; make a new post aka "comment". That way you can prefix it with some friendly words and also I am not sure whether users are notified when you edit an existing post to include their handle. |
Yeah, great call.
Will do!
Yeah, I don't think people will get notification if you edit existing post which is fine because I want .a complete and organized list before I can invite/ask them later on. :) BTW, some of them are missing. I am still looking for it though. 😕 |
Ah okay. Makes sense. Not sure it works that way though. You might already have invited them just now. 😜 |
Okay, I have a full list here. But with two unknown contributors.
Oh, really?? 😳 I thought it wouldn't notify by editing the existing post... hmm... I mean if they read through the thread they might already know what to do. I will still add some more information just in case if anyone came here is confused. 😄 |
I'm okay with signing the copyright assignment 👍 I hope it's enough to do them electronically, feel free to send me the documents via E-Mail. |
Basically, everyone has to follow the instructions here: https://code.orgmode.org/bzg/org-mode/raw/master/request-assign-future.txt But you might check with emacs-devel first (maybe the form has changed lately, though I doubt that). |
A previous link mentions:
With a one line diff, can I unsubscribe from this issue? :) |
Cool, I have emailed to assign@gnu.org and do get the pdf document to sign. The whole process is simple. :) @ramnes I think you could? I will check the checkbox indicate that you will pass this process. |
@jcs090218 The same for me, the change is small enough :) |
@markus1189 Got it! Thanks! :) |
My only commit is the "Looking for new maintainer" commit. Also signed the papers anyway. |
I have a off-topic question which we shouldn't probably ask here.
How did you sign? Using GPG? Or by hand on a printed copy of it? If you signed by hand, then how did you send it? Emailed a digital copy of the paper? Or a traditional mail? And finally, what information did they ask for? |
@AkibAzmain It's been a while that I signed the paper. I think I printed out then scanned it back to PC. It shouldn't be that hard. :) |
@jcs090218 Thanks. Do you still plan to add popup.el to GNU ELPA? That would be a great addition. (Though it would be greater to implement child frames in terminal.) |
Yeah, we wish to add this package to help but many people haven't replied to this issue, so I don't know how long would it take to accomplish this... Not sure if a child frame can be implemented in the terminal though. |
It should be possible to implement child frame. According to Eli Zaretskii:
However, I think this discussion is completely off-topic here, since it has nothing to do with popup.el. |
Many third-party projects consider this as a de-facto popup library. It would be good to be able to use it everywhere, including Company, if only to spare the users from having to set up the same faces when different popups are used.
In order to do that, all non-trivial contributors would have to sign copyright assignments to FSF. Is that feasible?
If this goes through, I'll try to take care of the current display bugs. You have several long-standing ones, and I believe most (all?) of them are fixed in Company's popup now.
The text was updated successfully, but these errors were encountered: