FreeCAD website repository organisation and groups

[marcuspollio]

Hi everyone!

In order to kick start the migration of this new website repository, let's get organized a bit! 😃

Organisation

As part of the FreeCAD ecosystem and organisation, a similar structure to what is currently used for the other repositories is applied here as well.

That means, everyone is welcome to contribute and get engaged in the development in the same known FreeCAD framework (i.e. Maintainers, Licensing terms, Code of conduct, Contribution process, etc). In addition, @marcuspollio is the current temporary admin of this repository so the migration can happen.

Groups

In order to facilitate the development and clarify some who/what/how, contributors can express their interest in or their desire to review certain specific parts of the website project.

Current FreeCAD org Teams members already have certain roles applied. A new website team will soon be created.

A. Please let us know if you want to join this website team (notifications and roles)?

In addition to this general website team, here are the specific parts of the website project you can get involved in:

Click to open detailed list

	Parts	People interested	Reviewers
1.0	All default (English) content	@maxwxyz @PhoneDroid @hyarion @YosypC	@marcuspollio @chennes
1.1	Homepage	@yorikvanhavre
1.2	Features collection	@yorikvanhavre
1.3	Download collection	@yorikvanhavre
1.4	News collection	@concretedog
1.5	Community collection	@concretedog
1.6	Documentation collection	@concretedog
1.7	Donate collection	@concretedog
2.0	All translations	@chennes
2.1	中文 et al.
2.2	Español et al.
2.3	Français et al.	@yorikvanhavre
2.4	Português et al.	@yorikvanhavre
2.5	Deutsch et al.	@maxwxyz
2.6	日本語 et al.	@PhoneDroid
2.7	русский et al.
2.8	Türkçe et al.	@Reqrefusion
2.9	Italiano et al.
2.10	Polski et al.
2.11	To be added...
3.0	Graphic design and visual com	@maxwxyz @PhoneDroid @hyarion
3.1	Illustrations, photos	@maxwxyz
3.2	Animations, videos
3.3	Icons, 3D, other medias	@maxwxyz
4.0	All code and workflow	@PhoneDroid @YosypC	@marcuspollio
4.1	HTML and Hugo template
4.2	CSS and style
4.3	JavaScript
4.4	CMS
4.5	CI/CD, config, tools
5.0	Others	@maxwxyz @PhoneDroid	@marcuspollio
5.1	Triage
5.2	Testing	@YosypC
5.3	Guidelines
5.4	Organization

We can also add a CODEOWNERS file (see example for KiCAD repo) to help this process.

B. For those wanting to review some parts, please indicate if you are OK with being in the CODEOWNERS file?

Note that for both of these groups, you are free to leave or even return, please just inform so.

Currently, no regular meeting schedule is set. Please indicate whether you are interested in meetings and how you envision them taking place.

Thank you all, have fun contributing and keep freecading! 😉

[marcuspollio]

FYI @FreeCAD/maintainers @FreeCAD/design-working-group @FreeCAD/cad-working-group @prokoudine @concretedog @CRogersMedia @PhoneDroid @kaktusus @FC-FBXL5

[kaktusus]

I don’t have the capacity to initiate new projects.

However, I can occasionally take a look here and there, follow along, and share some of my slightly crazy opinions.

At the moment, I am focused on designing a red and NIR light illuminator, because it has the potential to do a lot of good for the human body. I want to experience it myself.

[PhoneDroid]

@marcuspollio About using the same framework - please
correct the repository name casing before it's too late.

Btw didn't we two wanna meet up in January or something?

[marcuspollio]

Hi!
The repository is now called "Website".
Yeah, I was wondering if you would come to FreeCAD day.
Meetings are not scheduled yet. We can use this repo (or maybe the Devtalk forum) in the meantime.
Have a good one!

[PhoneDroid]

Yeah, seems my reply didn't reach you at the time.
( ' I rarely use Discord ' )

Are you on any other platform btw?
( Any will real time chat xD )

[maxwxyz]

@marcuspollio interested in 1.x..., 2.5, 3.0, 3.1, 3.3, 5.x...

[PhoneDroid]

@marcuspollio For now I wanna stay in the whole loop, so:
1.x , 2.6 , 3.x , 4.x , 5.x

[chennes]

I'll probably end up coordinating with the translators, so better add my name to the team for 2.0. And I'm nosy and opinionated, so 1.0 as well :).

[hyarion]

I can chime in on 1.0 and 3.0 discussions

[yorikvanhavre]

I can help with 1.1, 1.2, 1.3, 2.3, 2.4

[Reqrefusion]

I'm getting a 2.8. I'd like to help others too, but I still don't think I understand the vision here. Also, I still think this draft site is very boring and soulless. The organization and other things aren't helping for this.

[concretedog]

1.4-1.7 inclusive are deffo my role. But also happy to chime in on any other areas if they need input

[YosypC]

Tuning in from a message on the DevelopersHandbook repo, where I expressed my concerns on the lack of documentation quality. I believe the website can be a starting point, and I suggest you to read my message there as it contains precious suggestions.

My extensive GitHub's issues marks me as a good candidate for beta testing (5.2 Group).
As I already have a Wiki profile, I express interest in Group 1.0.
I have coding knowledge, I could be of mild help in group 4.0.

I can't easily express detailed groups preference.

My forum profile should you want to contact me there.
Regarding contacts, how will meetings be organized? Where will notifications be sent? You can aswer broadly, as this is the first time I tangibly interface with the social aspect of FOSS.

[marcuspollio]

Welcome and thanks for joining!

Would you like to be added to the 1.6 Documentation collection as well?
Given your notes above, is there a particular area of interest you would like to focus on or start with?
The migration of this website project (from another repository) will need a bit more time, but as soon as more focused testing can be done, I will let you know. Meeting are not scheduled yet, that will need to be organized soon.
For the Development Handbook Documentation section, the content of the current DevHandbook repository with some tweaks will be used. So in the meantime, any improvements there will benefit here too. I will ping you then the PR for this section is out.
The other two pillars of documentation (User manual, and code reference/API) will be tackled later.
Have a good one!

[YosypC]

I guess that for now it's better if I maintain an indicative position rather than a specific one. When the time will come, we'll refine the details of my capabilites to better suit the needs of the project. It's now not very clear, to me, what the current steps are, and I want to avoid overlapping work.

[marcuspollio]

what the current steps are

If you mean the current steps for this website project, you can find the current WIP status on this migration task issue.

After these tasks are complete, I will create dedicated and detailed issues for each area/section/topic, so it is easier to keep track of things (instead of buried into some comments somewhere 😁).