[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jedit-devel
Subject:    Re: [ jEdit-devel ] A word on plugin repositories hosting (SourceForge, GitHub, GitLab, Bitbucket, .
From:       Eric Le Lay <dev () elelay ! fr>
Date:       2020-06-02 18:44:52
Message-ID: 20200602204452.00491dca () dulcinea ! localdomain
[Download RAW message or body]

Hi Björn,

thanks for the write-up.

If not already done, can you add other admins to github and bitbucket,
to reduce the bus factor? The gitlab jedit group is now owned by you,
Matthieu and me.

Good luck with the git conversion!

Cheers,

Le Tue, 2 Jun 2020 14:16:02 +0200,
Vampire <Vampire@jedit.org> a écrit :

> Hi there,
> 
> just wanted to leave some notes regarding plugin repositories from my
> point of view.
> 
> It was never a requirement to have plugin repositories hosted in our
> repository / project on SourceForge.
> It was just a convenient place to have it hosted without the need to
> create an own project just for a plugin and to be able to easily
> maintain plugins together.
> And it provides the hooks we can use for access control and mailing
> list sending.
> 
> Every plugin maintainer can maintain the code of his plugins wherever
> he wants, be it GitHub, GitLab, BitBucket, SourceForge or any other
> hosting platform the maintainer prefers, this shouldn't make any
> difference if he does not want to have the hooks and the central
> place.
> 
> Actually I registered the workspace "jedit-editor" on BitBucket (as
> "jedit" was already taken),
> the organization "jedit-editor" on GitHub (as "jedit" was already
> taken) and the group "jedit" on GitLab,
> so that we can on either of them also have a central place where
> things could be mirrored to or maintained there and still have a
> "central place".
> 
> I just have those set to "private", because there is nothing in there
> yet, but I wanted to eventually keep read-only mirrors for the main
> jEdit code there too after I finally finished the Git migration and
> this time not so buggy as with the last try. Actually I fixed some of
> the migration issues and am working on the migration again right now,
> so I can hopefully finally finish it, I just had to have a total
> break from it the last months (please don't ask, this is not some
> laundry to make on the list).
> 
> 
> 
> Actually if I would maintain anything somewhere else than on
> SourceForge, I would use GitHub.
> This due to serveral reasons, including GitLab support are morons and
> I find GitLab and BitBucket quite unusable and confusing compared to
> GitHub. Another point also being that GitHub actions are way more
> powerful than GitLab or BitBucket pipelines. For example with GitHub
> actions you can also run actions on macOS which none of the others
> provides yet. And reviews are way better on GitHub, especially as
> IntelliJ has a very great pull request integration for GitHub pull
> requests now (actually soon, 2020.2 will make it feature-complete).
> You can review PRs, make inline comments in the diff viewer, see
> others comments, and so on.
> 
> 
> 
> So long story cut short, if anyone wants to maintain a plugin on
> something else than SourceForge, sure, go on, if you want to maintain
> it under a shared workspace / group / organization so that you can
> easier maintain plugins together or similar, just give me a ping and
> I can make the BitBucket workspace and / or GitHub orgainzation
> public and grant access. I'll then also try again to get hold of the
> "jedit" namespace in case the current owner lost interest in the name
> in the meantime.
> 
> 
> Cheers
> Björn



-- 
-----------------------------------------------
jEdit Developers' List
jEdit-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jedit-devel

[prev in list] [next in list] [prev in thread] [next in thread]