Re: Tuxedo and reliability (Re: New kde.org/hardware webpage)

2020-01-30 Thread Philippe Cloutier

Le 2020-01-30 à 03:38, Vinzenz Vietzke a écrit :

Hi Philippe,

Am 29. Januar 2020 22:46:14 schrieb Philippe Cloutier 
:



2. What comes on these PC-s? Vendor-specific GNU/Linux distributions?

It seemed to be a normal OpenSUSE installation (you can choose 
between a few

distros, that's nice).

Exactly. What we do with all our pre-installations is this scheme:

Minimal distribution setup + desktop pattern/metapackage + 
additional drivers

needed for the machines.



And how are these drivers added?


We add repositories to the package management system (Apt/Rpm) and 
pull the packages in during install. So e.g. we're adding 
graphics.tuxedocomputers.com to keep back untested graphics driver 
versions.


These repositories are accessible for manual installations as well as 
our fully automated ones during the manufacturing process.



Thank you Vinzenz. I would suggest to make that information available on 
Tuxedo's website. Unless it is already, in which case I find it 
difficult to find.





Cheers,
vinz.



--
Philippe Cloutier
http://www.philippecloutier.com



Re: Sysadmin Load Reduction: Legacy Compatibility Redirects

2020-01-30 Thread Zoltan Padrah
Ben Cooksley  ezt írta (időpont: 2019. nov. 9., Szo,
2:02):

> Hi all,
>
> One of the more smaller things that Sysadmin currently looks after is
> a large number of legacy compatibility redirects, which keep a variety
> of subdomains under KDE.org functional.
>
> For the most part these refer to dead projects, and have been legacy
> compatibility redirects for many years (5+) now.
>
> Given that sites should have now had a chance to update themselves,
> i'd like to go ahead and remove a number of these redirects.
>
> These redirects, whilst appearing relatively minor in nature, do
> require a certain degree of custom logic on the server side to handle
> them and therefore collectively create maintenance burden that in many
> cases probably outweighs the value they provide.
>
> We therefore should only retain them if there are places we are still
> unable to update which someone may need to follow (and not simply
> because 'somewhere might still link there') given that most people
> find things through their preferred search engine now.
>
> Below are a list of all the redirect candidates:
> --
>
> ...

> windows.kde.org
> mac.kde.org

...

>
> --
>
> Any comments?
>
> I'd also like to be able to recommend to the KDE e.V. Board that we
> permit kdepim.org, kdepim.com and korganizer.org to expire at the end
> of their current registration period.
>
> Thanks,
> Ben
>


Hi,

sorry for posting in this old thread, but I have just noticed that

https://kde.org/download/

still directly links windows.kde.org and mac.kde.org ; neither existing any
more. I do not know who to ping about updating the download web-page so I'm
writing here.


Best regards,

 Zoltan


Re: A safe haven for the community's memories

2020-01-30 Thread Ben Cooksley
On Thu, Jan 30, 2020 at 7:24 PM Piyush Aggarwal
 wrote:
>
> Hi Ben,

Hi Piyush,

>
> On Wed, 29 Jan, 2020, 2:42 PM Ben Cooksley,  wrote:
>>
>> On Wed, Jan 29, 2020 at 5:16 AM Piyush Aggarwal
>>  wrote:
>> >
>> >   Thanks for taking this discussion forward, Adriaan and Carl.
>> >
>> > On Mon, 27 Jan 2020 at 14:24, Adriaan de Groot  wrote:
>> >>
>> >> On Monday, 27 January 2020 07:27:42 CET Piyush Aggarwal wrote:
>> >> > > Almost always, photographs, videos and other forms of digital 
>> >> > > memorabilia
>> >> > > are so badly dispersed among the attendees, many of us have barely any
>> >> > > photographs from the event. The only way to get the photos we want is 
>> >> > > by
>> >> > > immediately getting the photographs on our phone then and there, 
>> >> > > during
>> >> > > the
>> >> > > event. The alternative after the event concludes and everyone is back 
>> >> > > home
>> >> > > safely, is to expect the sender to send the photographs as a mail
>> >> > > attachment or some other way that is generally a pain.
>> >> > > So, this mail thread aims to initiate a discussion on the prospect of
>> >> > > setting up a Kloud, of sorts.
>> >> ...
>> >> > > The current best solution as far as I know, is https://share.kde.org ,
>> >> > > which is limited to just 100 MB.
>> >> > > Would it be feasible for the KDE Community, especially our sysadmins, 
>> >> > > to
>> >> > > host a server for this purpose? :-)
>> >> > >
>> >> > > References
>> >> > > [1] : https://las2019.bcnfs.org/doku.php?id=wiki:lasphotos
>> >>
>> >> There was a discussion -- it's a sysadmin ticket, I don't know if it's
>> >> readable for all -- at https://phabricator.kde.org/T12026 for a similar
>> >> situation with LAS photos. Not the *same*, though, since that was also for
>> >> "raw" materials to be shared with video editors and other PR people.
>> >
>> >
>> > I cannot access that task, Adriaan. Perhaps if the task does not include 
>> > any sensitive content, we can put it on the promo task board for everyone 
>> > to help us with? :-)
>>
>> Please note that Sysadmin tasks are shielded by mechanisms that mean
>> placing it on another board will not make it accessible to others (so
>> adding it to the Promo board will not make it accessible to you)
>
>
> I understand that. I thought the part where this task is opened for everyone 
> to view was implicit in my earlier statement (if there is no sensitive 
> content, as I said). I personally think this problem deserves a task of its 
> own, and the idea to have a task for this on the promo board was not mine 
> alone, but rather suggested by Paul.
>

That task was regarding us getting bulk storage support for
share.kde.org, mainly to allow for us to handle large amounts of data
such as raw video footage.
Because this request is different, it should be handled through it's own ticket.

We will need to set this up as a separate set of shared folders
though, rather than one under the existing Promo hierarchy, as it will
need to be on bulk storage rather than the direct local system storage
(which is where the existing Promo folder lives)

>>
>> > Anyways, after some discussions with Paul, I think we have a solution for 
>> > future events.
>> > The Photos folder on share.kde.org currently hosts photographs for Promo 
>> > sprint (Barcelona,2018), Akademy (Vienna,2018), FOSDEM (Brussels, 2019) 
>> > and this year's conf.kde.in (Delhi).
>> > share.kde.org also has good support in terms of user access control- users 
>> > can be limited to adding new photographs, but not deleting any already 
>> > uploaded files. I can confirm this works just as expected.
>> > So, the solution proposed here is- we can share read & upload-only 
>> > permissions to the Photos folder to all KDE identities, and create a new 
>> > folder per-event.
>> > Would that be feasible?
>>
>> Access to share.kde.org is currently limited to developers and other
>> community members.
>
>
> That is true. I believe KDE events make use of events.kde.org and 
> reimbursements.kde.org infrastructure that both require an identity to be 
> able to register for an event and/ or ask for any reimbursements 
> respectively. Does that leave any possible uploaders?

There is a distinction for Identity purposes - general users of
Identity cannot login to share.kde.org.
Only developers have automatic access to share.kde.org. Everyone else
needs to apply to Sysadmin (via a ticket) to be given access.

As share.kde.org is only really usable if you have access to one of
the shared folders, this model has not caused any issues to date
(because they have to ask for access to those folders, which is when
we give them access if they're not a developer)

(This was a decision made to ensure it wasn't abused to distribute
material that is illegal / offensive / not in keeping with the values
of the community)

>
> Best
> Piyush Aggarwal

Cheers,
Ben


Re: Tuxedo and reliability (Re: New kde.org/hardware webpage)

2020-01-30 Thread Vinzenz Vietzke

Hi Philippe,

Am 29. Januar 2020 22:46:14 schrieb Philippe Cloutier :



2. What comes on these PC-s? Vendor-specific GNU/Linux distributions?

It seemed to be a normal OpenSUSE installation (you can choose between a few
distros, that's nice).

Exactly. What we do with all our pre-installations is this scheme:

Minimal distribution setup + desktop pattern/metapackage + additional drivers
needed for the machines.



And how are these drivers added?


We add repositories to the package management system (Apt/Rpm) and pull the 
packages in during install. So e.g. we're adding 
graphics.tuxedocomputers.com to keep back untested graphics driver versions.


These repositories are accessible for manual installations as well as our 
fully automated ones during the manufacturing process.


Cheers,
vinz.