[prev in list] [next in list] [prev in thread] [next in thread]
List: jedit-devel
Subject: Re: [ jEdit-devel ] spoiled by github
From: Alan Ezust <alan.ezust () gmail ! com>
Date: 2019-12-11 21:57:49
Message-ID: CALy5K9p1-RMVzXqsgk7kj-nkTPbqUOAmb0MnXU7TS8RYzt3pTA () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
Speaking of hooks, I haven't seen any e-mails about the XML plugin. Could
someone make sure that repo is sending the proper e-mails and has the same
hooks that all the other git repos for jedit have?
On Mon, Dec 9, 2019 at 8:32 AM Bj=C3=B6rn Kautler <Bjoern@kautler.net> wrot=
e:
> > And that's when sourceforge's lack of merge/pull requests hit me:
>
> But it has.
> You can fork a Git repository and create merge requests since long ago.
>
> > Not a pleasant tooling. The only upside is that all
> > changes are posted to the mailing list and Alan could cheer us :-).
>
> There are other upsides, like complete control over the repos and hooks
> and so on.
> We e. g. have hooks that ensure proper e-mail addresses being used as
> author and committer.
> And we have hooks that allow you to give specific users push rights and s=
o
> on.
> All this you cannot do with GitHub or GitLab.
>
> > So I'm considering moving the XML plugin to gitlab, to let Conal fork
> > and submit merge requests and we can discuss the code in place.
> >
> > Has anybody felt the same way?
>
> I really think it would be better to have the code where it is, especiall=
y
> as there we have much more freedom and also forks and merge requests. :-)
>
> > Any interest in creating a jEdit group on gitlab.com, so we can
> administer 'official' repositories together?
> > By the way, https://gitlab.com/jedit is already taken but maybe private=
.
> > Is it by one of us?
>
> Yes. :-)
>
> Am Mo., 9. Dez. 2019 um 14:47 Uhr schrieb Eric Le Lay <dev@elelay.fr>:
>
>> Hi,
>>
>> Thanks to Conal, I got back to the XML plugin again, after a few years
>> interruption. He did the right thing: submit a ticket in the correct
>> tracker with attached diff. Only a few adjustments needed to be
>> done to improve it.
>>
>> And that's when sourceforge's lack of merge/pull
>> requests hit me:
>> - no way to comment the code inline;
>> - no way to see the patch in context: download and apply it
>> to my checkout manually (patch -p0);
>> - no way to see diffs between diffs.
>>
>> Not a pleasant tooling. The only upside is that all
>> changes are posted to the mailing list and Alan could cheer us :-).
>>
>> So I'm considering moving the XML plugin to gitlab, to let Conal fork
>> and submit merge requests and we can discuss the code in place.
>>
>> Has anybody felt the same way? Any interest in creating a jEdit group
>> on gitlab.com, so we can administer 'official' repositories together?
>> By the way, https://gitlab.com/jedit is already taken but maybe private.
>> Is it by one of us?
>>
>> --
>> Eric
>>
>>
>> --
>> -----------------------------------------------
>> jEdit Developers' List
>> jEdit-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>>
> --
> -----------------------------------------------
> jEdit Developers' List
> jEdit-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>
[Attachment #5 (text/html)]
<div dir="ltr"><div>Speaking of hooks, I haven't seen any e-mails about the XML \
plugin. Could someone make sure that repo is sending the proper e-mails and has the \
same hooks that all the other git repos for jedit \
have?</div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div \
dir="ltr" class="gmail_attr">On Mon, Dec 9, 2019 at 8:32 AM Björn Kautler <<a \
href="mailto:Bjoern@kautler.net">Bjoern@kautler.net</a>> \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">> \
And that's when sourceforge's lack of merge/pull requests hit \
me:<br><div><br></div><div>But it has.</div><div>You can fork a Git repository and \
create merge requests since long ago.<br></div><br> > Not a pleasant tooling. The \
only upside is that all<br>> changes are posted to the mailing list and Alan could \
cheer us :-).<br> <div><br></div><div>There are other upsides, like complete control \
over the repos and hooks and so on.</div><div>We e. g. have hooks that ensure proper \
e-mail addresses being used as author and committer.</div><div>And we have hooks that \
allow you to give specific users push rights and so on.</div><div>All this you cannot \
do with GitHub or GitLab.<br></div><div><br></div> > So I'm considering moving \
the XML plugin to gitlab, to let Conal fork<br>> and submit merge requests and we \
can discuss the code in place.<br> <div>> <br></div><div>> Has anybody felt the \
same way?</div><div><br></div><div>I really think it would be better to have the code \
where it is, especially as there we have much more freedom and also forks and merge \
requests. :-)<br></div><div><br></div><div>> Any interest in creating a jEdit \
group on <a href="http://gitlab.com" rel="noreferrer" target="_blank">gitlab.com</a>, \
so we can administer 'official' repositories together?<br></div>> By the \
way, <a href="https://gitlab.com/jedit" rel="noreferrer" \
target="_blank">https://gitlab.com/jedit</a> is already taken but maybe \
private.<br><div>> Is it by one of us?</div><div><br></div><div>Yes. :-)<br></div>
</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Am Mo., 9. Dez. \
2019 um 14:47 Uhr schrieb Eric Le Lay <<a href="mailto:dev@elelay.fr" \
target="_blank">dev@elelay.fr</a>>:<br></div><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">Hi,<br> <br>
Thanks to Conal, I got back to the XML plugin again, after a few years<br>
interruption. He did the right thing: submit a ticket in the correct<br>
tracker with attached diff. Only a few adjustments needed to be<br>
done to improve it.<br>
<br>
And that's when sourceforge's lack of merge/pull<br>
requests hit me:<br>
- no way to comment the code inline;<br>
- no way to see the patch in context: download and apply it<br>
to my checkout manually (patch -p0);<br>
- no way to see diffs between diffs.<br>
<br>
Not a pleasant tooling. The only upside is that all<br>
changes are posted to the mailing list and Alan could cheer us :-).<br>
<br>
So I'm considering moving the XML plugin to gitlab, to let Conal fork<br>
and submit merge requests and we can discuss the code in place.<br>
<br>
Has anybody felt the same way? Any interest in creating a jEdit group<br>
on <a href="http://gitlab.com" rel="noreferrer" target="_blank">gitlab.com</a>, so we \
can administer 'official' repositories together?<br> By the way, <a \
href="https://gitlab.com/jedit" rel="noreferrer" \
target="_blank">https://gitlab.com/jedit</a> is already taken but maybe private.<br> \
Is it by one of us?<br> <br>
--<br>
Eric<br>
<br>
<br>
-- <br>
-----------------------------------------------<br>
jEdit Developers' List<br>
<a href="mailto:jEdit-devel@lists.sourceforge.net" \
target="_blank">jEdit-devel@lists.sourceforge.net</a><br> <a \
href="https://lists.sourceforge.net/lists/listinfo/jedit-devel" rel="noreferrer" \
target="_blank">https://lists.sourceforge.net/lists/listinfo/jedit-devel</a><br> \
</blockquote></div>
-- <br>
-----------------------------------------------<br>
jEdit Developers' List<br>
<a href="mailto:jEdit-devel@lists.sourceforge.net" \
target="_blank">jEdit-devel@lists.sourceforge.net</a><br> <a \
href="https://lists.sourceforge.net/lists/listinfo/jedit-devel" rel="noreferrer" \
target="_blank">https://lists.sourceforge.net/lists/listinfo/jedit-devel</a><br> \
</blockquote></div>
--
-----------------------------------------------
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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic