On Sun, Jun 21, 2020 at 10:34 AM Waqas Hussain wrote:
> On Tue, Jun 16, 2020 at 1:13 PM Jonas Schäfer wrote:
>
>> > Alternatively, if we do still want to use Docker, why not just use
>> > whatever GitHub's CI is or one of the many CI solutions that can work
>> > with GitHub without setting up
On Tue, Jun 16, 2020 at 1:13 PM Jonas Schäfer wrote:
> > Alternatively, if we do still want to use Docker, why not just use
> > whatever GitHub's CI is or one of the many CI solutions that can work
> > with GitHub without setting up lots of new infrastructure, repos,
> > syncing, etc? (ie.
On 2020/06/16, Jonas Schäfer wrote:
> Hi again,
>
> Thanks Sam and Kevin for your valuable feedback. I think what you say
> definitely has merit.
>
> In light of that, we came up with a hybrid solution which may be better or
> worse. We need input on that.
>
> [..]
>
> Again, thank you very
My original emails were from a former editors point of view and I don't
have particularly strong feelings except that we should keep the setup
simple and not move the code away from where the contributors are.
However, Jonas asked for contributor points of view. As a contributor I
have had the
My two cents on this:
I'm neither involved with the editors team nor am I a huge CI expert. All I can
say is that if the editors team benefits from a switch then I'm all for it.
I also like the move from the perspective of decentralization, even if we
"just" move from the biggest provider to
I suspect most people have no strong opinion on this either way (it doesn't
directly affect them) - hence the quite narrow responses.
So, to unironically signal my own nonchalance, I'm responding.
That said, anything which improves the editor process, particularly reducing
required time and
Hey,
I think there is considerable merit in moving to Gitlab - I've found it
impressive to use "in anger" as a product, and the technical abilities that
Jonas outlined below are mouth-wateringly exciting, but also it feels
generally more aligned to our FLOSS-friendly stance as an organisation.
On Sun Jun 14, 2020 at 6:31 PM CEST, Jonas Schäfer wrote:
> Dear community members,
>
> TL;DR: Due to considerable technical advantages, the Editor team is
> considering moving the repositories currently hosted at
> github.com/xsf/xeps adn gitlab.com/xsf/registrar to gitlab.com/xsf.
> This will
+1 for a full migration to Gitlab. No mirroring to Github. No
nonsense. Anything that will help our editors.
___
Standards mailing list
Info: https://mail.jabber.org/mailman/listinfo/standards
Unsubscribe: standards-unsubscr...@xmpp.org
The permissions form is confusing, but I don't think this is true, I've
definitely got Travis at least setup on single organizations. If
something weird has changed and this is true, we could also create an
"XSF Bot" account or something and then it's not a problem because the
bot only has access
Hi Guus,
Also thanks to you for more feedback.
On Dienstag, 16. Juni 2020 19:06:04 CEST Guus der Kinderen wrote:
> Thanks for all of the effort that you're putting into this. A concern that
> I have with the shared gitlab/github solution is that it has a lot of
> moving parts, a lot of
Hi Sam,
Thanks again for your feedback.
On Dienstag, 16. Juni 2020 19:03:40 CEST Sam Whited wrote:
> This seems like a lot of extra maintenance burden and a very complicated
> solution (and this is why editors get burnt out and we go through them,
> the whole process was already somewhat
Hi Jonas,
Thanks for all of the effort that you're putting into this. A concern that
I have with the shared gitlab/github solution is that it has a lot of
moving parts, a lot of dependencies, and a lot of places where things can
go wrong. Complexity of the implementation increases (to save
This seems like a lot of extra maintenance burden and a very complicated
solution (and this is why editors get burnt out and we go through them,
the whole process was already somewhat complicated). If Docker doesn't
actually make things easier for us, maybe we shouldn't use it.
Alternatively, if
Hi again,
Thanks Sam and Kevin for your valuable feedback. I think what you say
definitely has merit.
In light of that, we came up with a hybrid solution which may be better or
worse. We need input on that.
- We keep the GitHub xeps (and registar) repositories.
- We create mirror repositories
Hi Jonas,
I agree with Sam that it is very desirable for PRs to be accepted on github,
for the sake of contribution to the XSF - I *really* would not like to see the
repo move. If it’s at all practical for us to stay there, I think that is the
best option.
That said, if there is no other
On Sonntag, 14. Juni 2020 17:17:44 CEST Sam Whited wrote:
> Ahh, I see, this is a Docker Hub issue. I completely agree that Docker
> Hub has not been a success. It is also quite easy to build Docker
> images with other CI platforms though while remaining on GitHub (ie. I
> think you already
Ahh, I see, this is a Docker Hub issue. I completely agree that Docker
Hub has not been a success. It is also quite easy to build Docker
images with other CI platforms though while remaining on GitHub (ie. I
think you already submitted a PR to use a GitLab CI build). I've built
Docker images with
Hi Sam,
Thank you for your feedback. I hear you. I totally see where you’re coming
from. Moving off GitHub, which is, as you say, where the people are, is a
thing which needs to be considered carefully. Ultimately, the Board will have
to decide (hence also CC to members@).
First of all,
What are the technical advantages?
Also just in general, I completely disagree. We need to be where the
people are, and the people are on GitHub whether we like it or not.
Don't split up the repos and make XSF resources even harder to find than
they already are, don't make things more complicated
Dear community members,
TL;DR: Due to considerable technical advantages, the Editor team is
considering moving the repositories currently hosted at github.com/xsf/xeps
adn gitlab.com/xsf/registrar to gitlab.com/xsf. This will reduce delays in
processing XEP changes and revive the Registry.
21 matches
Mail list logo
