Re: [HelenOS-devel] Switching away from Trac?

2018-11-30 Thread Jiri Svoboda

Jakub wrote:


> Well, I wouldn't go as far as running our vital infrastructure on
"HelenOS yet :-)"



Why not?




-Jiri
___
HelenOS-devel mailing list
HelenOS-devel@lists.modry.cz
http://lists.modry.cz/listinfo/helenos-devel


Re: [HelenOS-devel] Switching away from Trac?

2018-11-29 Thread Jiri Svoboda

I think the problem is rather that a *single* administrator is a single 
point of failure. I don't have any doubt that any person from the core team
would have the skills and knowledge to step up as administrator if needed,
provided that he is given the necessary information and authorization.




-Jiri


On Thu, 29 Nov 2018 at 10:14, Jiri Svoboda  wrote:
">
> Exactly. I don't want to rely on GH too much. I'd prefer if we are able to
self-host all crucial infrastructure, like code and issues. I don't care so
much which system we use as long as it's owned by us. I'm still hoping to 
see trac show git commits ;-)
>

Self-hosting crucial infrastructure requires having an administrator
able to maintain its function.
With all due respect to Martin's efforts, we clearly don't have anyone
with both time and expertise to do it, and the current state of
helenos.org reflects that issue.

-- jzr

___
HelenOS-devel mailing list
HelenOS-devel@lists.modry.cz
http://lists.modry.cz/listinfo/helenos-devel
"___
HelenOS-devel mailing list
HelenOS-devel@lists.modry.cz
http://lists.modry.cz/listinfo/helenos-devel


Re: [HelenOS-devel] Switching away from Trac?

2018-11-29 Thread Jiří Zárevúcky
On Thu, 29 Nov 2018 at 10:14, Jiri Svoboda  wrote:
>
> Exactly. I don't want to rely on GH too much. I'd prefer if we are able to 
> self-host all crucial infrastructure, like code and issues. I don't care so 
> much which system we use as long as it's owned by us. I'm still hoping to see 
> trac show git commits ;-)
>

Self-hosting crucial infrastructure requires having an administrator
able to maintain its function.
With all due respect to Martin's efforts, we clearly don't have anyone
with both time and expertise to do it, and the current state of
helenos.org reflects that issue.

-- jzr

___
HelenOS-devel mailing list
HelenOS-devel@lists.modry.cz
http://lists.modry.cz/listinfo/helenos-devel


Re: [HelenOS-devel] Switching away from Trac?

2018-11-29 Thread Jakub Jermář
On 11/29/18 10:13 AM, Jiri Svoboda wrote:
> Exactly. I don't want to rely on GH too much. I'd prefer if we are able
> to self-host all crucial infrastructure, like code and issues. I don't
> care so much which system we use as long as it's owned by us. I'm still
> hoping to see trac show git commits ;-)

Our current infrastructure is currently lacking maintenance and it is
difficult to get anything done on it. GH makes it easy to have multiple
people who can actually make changes. I wouldn't want to go back to the
model when it was not possible to even authenticate via a ssh key when
pushing to the repo, not speaking of being able to easily manage commit
access for others. Having said that, I don't see having trac support for
git commits or https access anytime soon, but I can be wrong :-)

> I'd strongly prefer not to have a split brain situation with using both
> track tickets and GH issues.

Okay, I disabled that again in the morning. But I would actually prefer
to have it the other way around.

Jakub

> 
> Cheers,
> Jiri
> -- Původní e-mail --
> Od: Vojtech Horky 
> Komu: HelenOS development mailing list 
> Datum: 29. 11. 2018 0:12:35
> Předmět: Re: [HelenOS-devel] Switching away from Trac?
> 
> 
> čt 29. 11. 2018 v 0:01 odesílatel Jakub Jermář  napsal:
> > On 11/28/18 11:54 PM, Vojtech Horky wrote:
> > > are we preparing to abandon our Trac instance? Because I received
> > > 100+ e-mails from prehistoric Trac issues generated by GitHub. It
> > > seemed to me as someone was trying to do mass export-import?
> >
> > It was me. I was experimenting a little, but my conversion script was
> > stopped by GitHub abuse detection mechanism (despite measures to
> > throttle down the request rate) after some 50 tickets were converted.
> > Sorry for all the e-mail notifications.
> 
> No problem :-)
> 
> > After this experiment, I don't think it is realistic to import the
> Trac
> > tickets into GitHub. But we can keep the issues enabled and use
> them in
> > parallel and later as a replacement to Trac.
> 
> Any particular reason why do you want to replace Trac? I thought that
> we want eventually to have master back on helenos.org and have GH as a
> backup.
> 
> - Vojta
> 
> ___
> HelenOS-devel mailing list
> HelenOS-devel@lists.modry.cz
> http://lists.modry.cz/listinfo/helenos-devel
> 
> 
> ___
> HelenOS-devel mailing list
> HelenOS-devel@lists.modry.cz
> http://lists.modry.cz/listinfo/helenos-devel
> 

___
HelenOS-devel mailing list
HelenOS-devel@lists.modry.cz
http://lists.modry.cz/listinfo/helenos-devel


Re: [HelenOS-devel] Switching away from Trac?

2018-11-29 Thread Jakub Jermář
Hi Jiri,

On 11/29/18 10:17 AM, Jiri Svoboda wrote:
> Hi Jakub,
> 
>> All this experimenting and thinking is motivated by ending up with a
>> statically generated helenos.org eventually served by HelenOS itself.
> 
> No, please. It's completely unnecessary to cripple helenos.org for that
> reason. We have a python port, don't we? Integrating it with our web
> server and getting trac to work shouldn't be that difficult.

Well, I wouldn't go as far as running our vital infrastructure on
HelenOS yet :-) But hosting a static home page and having the vital
infrastructure elsewhere sounds more feasible.

Jakub

___
HelenOS-devel mailing list
HelenOS-devel@lists.modry.cz
http://lists.modry.cz/listinfo/helenos-devel


Re: [HelenOS-devel] Switching away from Trac?

2018-11-29 Thread Jiri Svoboda

Hi Jakub,




> All this experimenting and thinking is motivated by ending up with a
> statically generated helenos.org eventually served by HelenOS itself. 





No, please. It's completely unnecessary to cripple helenos.org for that 
reason. We have a python port, don't we? Integrating it with our web server
and getting trac to work shouldn't be that difficult.




Regards,

Jiri

-- Původní e-mail --
Od: Jakub Jermář 
Komu: HelenOS development mailing list 
Datum: 29. 11. 2018 9:15:51
Předmět: Re: [HelenOS-devel] Switching away from Trac?
"On 11/29/18 12:11 AM, Vojtech Horky wrote:
> Any particular reason why do you want to replace Trac? I thought that 
> we want eventually to have master back on helenos.org and have GH as a 
> backup.

Well, on GH everything is nicely integrated together - commits, pull
requests and issues. It might be easier for people to use GH issues with 
their existing GH account than creating a dedicated HelenOS account on
our trac, then going through the surprise of having their access token
publicly sent to the ML. We wouldn't have to be on guard for new
suspiciously looking spam accounts. Most of the time, GH would be just
up and we wouldn't have to maintain it. It would be also easier to use
it for us - how many time have people wanted to add a new trac ticket
category, but could not because of lacking admin privileges?

I have been backing most of our GH repos automatically on GitLab[1] for 
some time now. We could later do the same with our own Git server, maybe 
on a private instance of GitLab, but I am beginning to miss the point
with all these backups lying around.

All this experimenting and thinking is motivated by ending up with a
statically generated helenos.org eventually served by HelenOS itself.

Jakub

[1] https://gitlab.com/HelenOS

___
HelenOS-devel mailing list
HelenOS-devel@lists.modry.cz
http://lists.modry.cz/listinfo/helenos-devel
"___
HelenOS-devel mailing list
HelenOS-devel@lists.modry.cz
http://lists.modry.cz/listinfo/helenos-devel


Re: [HelenOS-devel] Switching away from Trac?

2018-11-29 Thread Jiri Svoboda

Exactly. I don't want to rely on GH too much. I'd prefer if we are able to
self-host all crucial infrastructure, like code and issues. I don't care so
much which system we use as long as it's owned by us. I'm still hoping to 
see trac show git commits ;-)




I'd strongly prefer not to have a split brain situation with using both 
track tickets and GH issues.





Cheers,

Jiri

-- Původní e-mail --
Od: Vojtech Horky 
Komu: HelenOS development mailing list 
Datum: 29. 11. 2018 0:12:35
Předmět: Re: [HelenOS-devel] Switching away from Trac?
"čt 29. 11. 2018 v 0:01 odesílatel Jakub Jermář  napsal:
> On 11/28/18 11:54 PM, Vojtech Horky wrote:
> > are we preparing to abandon our Trac instance? Because I received
> > 100+ e-mails from prehistoric Trac issues generated by GitHub. It
> > seemed to me as someone was trying to do mass export-import?
>
> It was me. I was experimenting a little, but my conversion script was
> stopped by GitHub abuse detection mechanism (despite measures to
> throttle down the request rate) after some 50 tickets were converted.
> Sorry for all the e-mail notifications.

No problem :-)

> After this experiment, I don't think it is realistic to import the Trac
> tickets into GitHub. But we can keep the issues enabled and use them in
> parallel and later as a replacement to Trac.

Any particular reason why do you want to replace Trac? I thought that
we want eventually to have master back on helenos.org and have GH as a
backup.

- Vojta

___
HelenOS-devel mailing list
HelenOS-devel@lists.modry.cz
http://lists.modry.cz/listinfo/helenos-devel
"___
HelenOS-devel mailing list
HelenOS-devel@lists.modry.cz
http://lists.modry.cz/listinfo/helenos-devel


Re: [HelenOS-devel] Switching away from Trac?

2018-11-29 Thread Jakub Jermář
On 11/29/18 12:11 AM, Vojtech Horky wrote:
> Any particular reason why do you want to replace Trac? I thought that
> we want eventually to have master back on helenos.org and have GH as a
> backup.

Well, on GH everything is nicely integrated together - commits, pull
requests and issues. It might be easier for people to use GH issues with
their existing GH account than creating a dedicated HelenOS account on
our trac, then going through the surprise of having their access token
publicly sent to the ML. We wouldn't have to be on guard for new
suspiciously looking spam accounts. Most of the time, GH would be just
up and we wouldn't have to maintain it. It would be also easier to use
it for us - how many time have people wanted to add a new trac ticket
category, but could not because of lacking admin privileges?

I have been backing most of our GH repos automatically on GitLab[1] for
some time now. We could later do the same with our own Git server, maybe
on a private instance of GitLab, but I am beginning to miss the point
with all these backups lying around.

All this experimenting and thinking is motivated by ending up with a
statically generated helenos.org eventually served by HelenOS itself.

Jakub

[1] https://gitlab.com/HelenOS

___
HelenOS-devel mailing list
HelenOS-devel@lists.modry.cz
http://lists.modry.cz/listinfo/helenos-devel


Re: [HelenOS-devel] Switching away from Trac?

2018-11-28 Thread Vojtech Horky
čt 29. 11. 2018 v 0:01 odesílatel Jakub Jermář  napsal:
> On 11/28/18 11:54 PM, Vojtech Horky wrote:
> > are we preparing to  abandon our Trac instance? Because I received
> > 100+ e-mails from prehistoric Trac issues generated by GitHub. It
> > seemed to me as someone was trying to do mass export-import?
>
> It was me. I was experimenting a little, but my conversion script was
> stopped by GitHub abuse detection mechanism (despite measures to
> throttle down the request rate) after some 50 tickets were converted.
> Sorry for all the e-mail notifications.

No problem :-)

> After this experiment, I don't think it is realistic to import the Trac
> tickets into GitHub. But we can keep the issues enabled and use them in
> parallel and later as a replacement to Trac.

Any particular reason why do you want to replace Trac? I thought that
we want eventually to have master back on helenos.org and have GH as a
backup.

- Vojta

___
HelenOS-devel mailing list
HelenOS-devel@lists.modry.cz
http://lists.modry.cz/listinfo/helenos-devel


Re: [HelenOS-devel] Switching away from Trac?

2018-11-28 Thread Jakub Jermář
Hi Vojta,

On 11/28/18 11:54 PM, Vojtech Horky wrote:
> are we preparing to  abandon our Trac instance? Because I received
> 100+ e-mails from prehistoric Trac issues generated by GitHub. It
> seemed to me as someone was trying to do mass export-import?

It was me. I was experimenting a little, but my conversion script was
stopped by GitHub abuse detection mechanism (despite measures to
throttle down the request rate) after some 50 tickets were converted.
Sorry for all the e-mail notifications.

After this experiment, I don't think it is realistic to import the Trac
tickets into GitHub. But we can keep the issues enabled and use them in
parallel and later as a replacement to Trac.

Jakub

___
HelenOS-devel mailing list
HelenOS-devel@lists.modry.cz
http://lists.modry.cz/listinfo/helenos-devel


[HelenOS-devel] Switching away from Trac?

2018-11-28 Thread Vojtech Horky
Hello,

are we preparing to  abandon our Trac instance? Because I received
100+ e-mails from prehistoric Trac issues generated by GitHub. It
seemed to me as someone was trying to do mass export-import?

- Vojta

___
HelenOS-devel mailing list
HelenOS-devel@lists.modry.cz
http://lists.modry.cz/listinfo/helenos-devel