Re: [open-regulatory-compliance] Collaborating using GitLab

[Tobie Langel <tobie@xxxxxxxxxxxxxx>]

Hi Italo, others,

Thank you, Italo, for your thoughtful email.

Choosing what tools to use is always a delicate exercise full of tradeoffs and conflicting requirements.

Given our constraints and given the work ahead of us (which implies substantial collection, curation, and centralisation of existing but fairly scattered information about both the CRA and development best practices), choosing to leverage markdown files hosted on GitLab and GitLab's issue tracker seems like a reasonable tradeoff. We're only relying on GitLab's web client, so there is no need to install or run anything on your machine.

Of course, it'll always be possible to use the mailing list to comment or make suggestions about work happening on GitLab.

For those who prefer a more hands on approach and aren't familiar with GitLab, these sessions are an opportunity to get up to speed more easily than having to figure out everything by themselves.

That said, everyone's of course welcome to attend those sessions in whatever capacity they chose. Hopefully, I'll get to see you later this evening or tomorrow.

Thanks again for raising this point on the list,

--tobie

On Tue, Aug 13, 2024 at 11:38 AM Italo Vignoli via open-regulatory-compliance <open-regulatory-compliance@xxxxxxxxxxx> wrote:

Hi Tobie,

I will attend the session (tonight or tomorrow), but please do not ask
me to become familiar with GitLab as I do not have any kind of technical
background and when I have tried to contribute to LibreOffice a senior
developer had to work hard to revert the mess I created.

The ORC WG is about creating a cybersecurity standard for open source
software, and you do not need to be a developer to contribute. I have a
solid experience about standardization process, and I manage standard
related issues on a regular basis (but to do this I do not have to make
any commit).

Believe me, even if you find software such as GitHub or GitLab trivial,
there are people who were born in the analog world and completely miss a
clue about development. I am regularly contributing to books in GitHub,
but after developers have realized the mess I can create with a basic
commit there is one of them doing the job for me.

Sorry, but going though a technical workflow is a bug of projects driven
by technical people. I am a Software Heritage Ambassador, and I had the
same issue with them, as they accepted contributions only via GitHub.
Today, they have changed and accept text based contributions.

So, I will attend the session as a watcher, as I want to understand how
the process works, but no hands-on for me.

Best regards, Italo

On 13/08/24 10:53, Tobie Langel via open-regulatory-compliance wrote:
> Hi all,
>
> Just a quick reminder that our first session is starting in 10 minutes:
> https://eclipse.zoom.us/j/87025539295
> <https://eclipse.zoom.us/j/87025539295>
>
> Join us!
>
> /(Note I'm running this same session again at 9pm CEST today and at 5pm
> CEST tomorrow if you can't make this one.) /
>
> --tobie
>
>
> On Sun, Aug 11, 2024 at 1:28 PM Tobie Langel <tobie@xxxxxxxxxxxxxx
> <mailto:tobie@xxxxxxxxxxxxxx>> wrote:
>
>     Hi all,
>
>     Thanks to all of you who replied to the Doodle poll.
>
>     I'll be running three sessions this week on collaborating using GitLab:
>
>       * *Tuesday, August 13 @ 11am CEST*
>       * *Tuesday, August 13 @ 9 pm CEST*
>       * *Wednesday, August 14 @ 5 pm CEST*
>
>     I've added those sessions to the community calendar
>     <https://calendar.google.com/calendar/u/0/embed?src="">>.
>
>     These will be hands-on, one hour sessions to get you up to speed on
>     using GitLab for effective collaboration within the ORC WG. During
>     this session you will:
>
>       * Set up your Eclipse account
>       * Learn Git, GitLab, and markdown basics
>       * Join ORC WG's GitLab project
>       * Create your first issue
>       * Create your first merge request (= pull request)
>       * Review someone's merge request
>       * Merge your first commit
>
>     *What to *_prepare_*for the session:*
>
>       * Read the Eclipse Foundation's CLA:
>         https://www.eclipse.org/legal/eca/
>         <https://www.eclipse.org/legal/eca/>
>       * Write down a question about the CRA you'd like to add to the FAQ
>         (we'll use this in our exercises)
>
>     Looking forward to seeing you there!
>
>     Best,
>
>     --tobie
>
>     ---
>     Tobie Langel
>     Tech Lead Open Regulatory Compliance WG, Eclipse Foundation
>     Principal, UnlockOpen
>
>     On Thu, Aug 8, 2024 at 6:33 PM Tobie Langel <tobie@xxxxxxxxxxxxxx
>     <mailto:tobie@xxxxxxxxxxxxxx>> wrote:
>
>         Hi all,
>
>         I'll be running a few sessions next week to get everyone up to
>         speed on collaborating using GitLab.
>
>         Please provide your availability using this link:
>         https://doodle.com/meeting/participate/id/eEGROr4b
>         <https://doodle.com/meeting/participate/id/eEGROr4b>
>
>         I'll be picking the 2-3 most popular choices and will be running
>         sessions at those times.
>
>         Looking forward to it,
>
>         --tobie
>
>         ---
>         Tobie Langel
>         Tech Lead Open Regulatory Compliance WG, Eclipse Foundation
>         Principal, UnlockOpen
>
>
> _______________________________________________
> open-regulatory-compliance mailing list
> open-regulatory-compliance@xxxxxxxxxxx
> To unsubscribe from this list, visit https://accounts.eclipse.org
--
Italo Vignoli - italo@xxxxxxxxxxx
mobile/signal +39.348.5653829
GPG Key ID - 0xAAB8D5C0
DB75 1534 3FD0 EA5F 56B5 FDA6 DE82 934C AAB8 D5C0

_______________________________________________
open-regulatory-compliance mailing list
open-regulatory-compliance@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org