-
Notifications
You must be signed in to change notification settings - Fork 62
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
Is this project a fork or the continuation of the original Scour project? #11
Comments
@Ede123 I had an email conversation about this with Jeff .. and in my reading, he was happy to handover (the concrete issue was me asking if it's ok to publish scour to PyPI). Here:
|
And here is a follow reply by me:
|
@Ede123 Maybe you could ask Jeff about his opinion. I will certainly do what he wants. I also don't care much .. we need this tool ourselves, so I took over because there were concrete issues. |
Thanks for info. I didn't intend to insinuate anything and I'd like to point out that I'm happy somebody is actively working on Scour since it was inactive for a long time before. However it would be unfortunate if two independent branches of Scour were developing because of a lack of communication. After all there are two code repositories right now and it's unclear which one is to be considered as "official" (probably both are somehow) and to which one one should contribute code to. If this ambiguity could be resolved and Scour could continue to be a single well defined project that would probably be the best solution. |
Yep, agreed. So what should we do? IMO, best for scour would be (Jeff @codedread ? What do you think?):
|
Sounds good to me! Only one note regarding closure of https://launchpad.net/scour. It might be that this repository is still needed to package Scour for Linux distros (I don't know anything about that, just to make you aware there might be an issue; I assume Jeff could comment on that). Will you contact Jeff regarding the open points? |
Mentioning @codedread should be enough to ping. maybe you could send him a quick mail in addition. when he's good, I can start the process by transferring the repo. |
Here is an alternative: transfer to https://github.com/inkscape/scour |
https://github.com/inkscape is not an official repository of the Inkscape project. |
Oh, ok. I see. Well, then not. I guess, Inkscape officially is on .. wait. LP;) Ok, then lets see what Jeff says. Anyway, I am ready. |
@Ede123 I didn't get any response. Closing .. |
Yes, too bad... I still hope for an answer by Jeff (maybe he's just too busy or on vacation right now) so we can really resolve the issue rather than just closing it... |
@Ede123 I agree, maybe too early to close .. but hey, we can reopen should we receive an answer. |
Hi there folks - sorry, I didn't respond earlier! Since I haven't contributed anything to Scour in years, I don't have a strong preference for what is about to happen. My personal opinion is that since oberstet has actually continued to make improvements to Scour and there hasn't been a launchpad commit in a year and a half, it seems like he is now the defacto owner of it. Because of this, moving things to github makes sense, since that is where oberstet wants it to be :) I think first step is to establish where on github it should belong. If folks want me to put it under github.com/codedread to establish legitimacy (whatever that means), I will agree to do so, but that would imply ownership and I don't particularly want to be involved in pull requests, etc. Assuming that oberstet will manage things. The current location also seems fine to me. Let me know. Just now I sent an email to the team that manages the Scour repo on launchpad letting them know of the plan. I will let folks know here if there are any objections to moving development to github (which has already happened). The final steps will be to close down the launchpad repo, disband the team and point my website at the github location (the easiest part). |
@codedread thanks! @Ede123 Having scour on "oberstet" or "coderead" seems both less desirable than having it under "inkscape". Let's try to fix it once for all: https://github.com/inkscape isn't official right now. IMO the Inkscape project should take ownership of that GH org name. I'm sure GH would do if asked by Inkscape project members. Are you a Inkscape project member? Then I transfer the repo to https://github.com/inkscape/scour |
@oberstet Why the focus on Inkscape? Scour is certainly used in Inkscape but in the end it's a stand-alone program. I don't think we should put it under the Inkscape umbrella (unless @codedread is in favor of such a transition). Therefore while I'm certain one could acquire @inkscape I don't see the need and it would be a tedious hassle to do the transition with the Inkscape project not actively using GitHub (find a project member in charge - I'm not a project member, just a volunteer contributor - get them to acquire the organization, find someone to take care of this organization from then on, etc.) Since @codedread is the original author, I think putting the repository there would be the logical solution (assuming you would continue to maintain it like you currently do, nothing really changes except the URL). |
@Ede123 @codedread I have initiated transfer of the repo to "coderead" .. @codedread you need to accept the transfer ("Repository transfer to codedread requested"), and I would need to have appropriate permissions on the repo to manage PRs and such. |
Thanks!
|
Looks like the transfer happened. And over here it says that @oberstet has push access to the repo: https://github.com/codedread/scour/settings/collaboration I'll wait a few more days before updating my website and closing the LP repo. |
@codedread awesome, thanks Jeff! that worked: I have push access, and the old repo location https://github.com/oberstet/scour automatically forwards to the new one https://github.com/codedread/scour |
@Ede123 alright, everything fine on your side? "official" enough? ;) |
Is this project to be understood as a fork or as the official continuation of the of the original Scour project?
There are also some uncertainties that could use clarification:
The text was updated successfully, but these errors were encountered: