#3 Take inventory of Fedora web development projects
Opened a year ago by jflory7. Modified a year ago

Summary

Complete an initial inventory and assessment of what web development projects there are in Fedora, and how ready a project is to accept new contributions.

Background

There are many web development projects in Fedora, but it is hard to know where they all are and which ones are active. To make it easier to discover opportunities to contribute to Fedora web apps, we need to explore what web dev projects are out there and make a list. We also need to note which ones are active and have folks who around to review new contributions.

Once we have an inventory of projects, we can then prioritize which ones to focus on or where are the best opportunities for people to get involved in new work.

Details

The deliverable for this would be a new documentation page that lists the different web app projects in Fedora. We could use a table of some kind to mark whether a web app is active, currently deployed, etc.

Long-term, we will use this list to filter down where we focus first as a SIG.

Outcome

Easier to understand what opportunities there are in Fedora to contribute as a web developer


@jflory7 @ramyaparimi

Do we consider the projects having the *.fedoraproject.org subdomain into account as well or is it something for the websites team to handle?

@t0xic0der If there are distinguishable front-end/back-end components (i.e. not only static sites), we can make note that they exist. There may be a few cases where we want to exclude a project, but I'd rather start with a big list and then narrow it down.

Yes, @jflory7 I am considering both static sites and dynamic apps/services.

I am currently gathering them all up in my personal kanban board before I
add it to our SIG's shared HackMD file.

I expect it to be a huge pile to start from. :P

On Tue, Mar 2, 2021 at 3:58 AM Justin W. Flory pagure@pagure.io wrote:

jflory7 added a new comment to an issue you are following:
@t0xic0der If there are distinguishable front-end/back-end components (i.e. not only static sites), we can make note that they exist. There may be a few cases where we want to exclude a project, but I'd rather start with a big list and then narrow it down.

To reply, visit the link below or just reply to this email
https://pagure.io/sig-webdev/home/issue/3

hey, I'd love to be able to help out with this if possible. Is there an area of the site that hasn't been mapped yet that I could start working through?

Hi @lilyx, thanks for picking this up. This task is currently in progress and the updates are in one of the HackMD.io files that we have scribbled into in the fast few weeks, so please feel free to jump right in and continue on from where we left off. I hope you are there in the Matrix channel for websites and apps for I would (most likely) find the document there. Let me check.

Hey @lilyx just checking in to see how it is going :grinning: Let us know if you need some help!

Metadata Update from @lilyx:
- Issue assigned to lilyx

a year ago

Login to comment on this ticket.

Metadata
Boards 1
WebDev Status: In Progress