Advertisement for FOSS used in infrastructure #506

Closed
opened 2008-04-15 19:22:00 +00:00 by pfrields · 13 comments

We need a way to show our love for the FOSS that we use every day to run our project... the software that you infrastructure and websites geniuses put together to make this the best damn project, EVAH. Some examples in alpha order:

  • Asterisk
  • MediaWiki
  • Trac
  • TurboGears

There are more, but you get the drift. We need to do this in a way that doesn't do a disservice to our paid sponsors -- i.e. the people who donate real $ cost equipment, e.g. Dell, Peer1, Red Hat, etc. That might be as simple as a separate page, with a link on fedoraproject.org/sponsors that points to "Fedora Proudly Runs...". Then logos with links, much like the normal sponsors.

(There could eventually be some really sweet docs out of this on putting together a hosted infrastructure built on free software.)

I'm going to TENTATIVELY put the milestone as Fedora 9 because this seems like a really quick fix. We can even add software as we go. But if the responsible individuals disagree, feel free to reassign to F10.

We need a way to show our love for the FOSS that we use every day to run our project... the software that you infrastructure and websites geniuses put together to make this the best damn project, EVAH. Some examples in alpha order: * Asterisk * MediaWiki * Trac * TurboGears There are more, but you get the drift. We need to do this in a way that doesn't do a *disservice* to our paid sponsors -- i.e. the people who donate real $$$ cost equipment, e.g. Dell, Peer1, Red Hat, etc. That might be as simple as a separate page, with a link on fedoraproject.org/sponsors that points to "Fedora Proudly Runs...". Then logos with links, much like the normal sponsors. (There could eventually be some really sweet docs out of this on putting together a hosted infrastructure built on free software.) I'm going to *TENTATIVELY* put the milestone as Fedora 9 because this seems like a really quick fix. We can even add software as we go. But if the responsible individuals disagree, feel free to reassign to F10.

Moving to F10 for now (not that there's any large disagreement)

Moving to F10 for now (not that there's any large disagreement)

This is something that can still be done on the wiki during our freeze if we have time for it. I'll try to add it to my list.

This is something that can still be done on the wiki during our freeze if we have time for it. I'll try to add it to my list.
Author

Replying to [comment:2 mmcgrath]:

This is something that can still be done on the wiki during our freeze if we have time for it. I'll try to add it to my list.

Any luck, or are your cycles all spoken for at this point?

Replying to [comment:2 mmcgrath]: > This is something that can still be done on the wiki during our freeze if we have time for it. I'll try to add it to my list. Any luck, or are your cycles all spoken for at this point?

man oh man do I need to sit down and do this.

man oh man do I need to sit down and do this.

Has there been any work on this one?

Maybe we should just discuss this in a meeting, or just use this ticket to compile the list?

Has there been any work on this one? Maybe we should just discuss this in a meeting, or just use this ticket to compile the list?
Owner

Problem mentioned at the last meeting this was discussed was that we often update or change software we are using, so it might be difficult to keep such a page up to date. :(

I'm happy to discuss at the next meeting and decide.

Problem mentioned at the last meeting this was discussed was that we often update or change software we are using, so it might be difficult to keep such a page up to date. :( I'm happy to discuss at the next meeting and decide.

Is this ticket still active? I'd love to sit down and work on it.

Is this ticket still active? I'd love to sit down and work on it.
Owner

It is. ;) One problem is how to figure out what we are actually using and keep such a page updated.

Perhaps we could look at all the stuff we install in ansible playbooks and base off that + things we have in our base installs.

It is. ;) One problem is how to figure out what we are actually using and keep such a page updated. Perhaps we could look at all the stuff we install in ansible playbooks and base off that + things we have in our base installs.
  • Trac
  • Git
  • Python
  • Ansible
  • Turbogears
  • Mediawiki
  • Askbot
  • Nagios?
  • Mailman (GNU)
  • Apache (httpd)

Am I missing anything?

- Trac - Git - Python - Ansible - Turbogears - Mediawiki - Askbot - Nagios? - Mailman (GNU) - Apache (httpd) Am I missing anything?
Owner

Well, it depends on what level we want to go to... ;)

Do we want to list the linux kernel? glibc? coreutils?

Or try and come up with some higher level critera?

Perhaps instead of trying to keep such a page fully up to date and list everything we could phrase it as:

"Fedora Infrastructure would like to thank the following projects for their software"

Thoughts?

Well, it depends on what level we want to go to... ;) Do we want to list the linux kernel? glibc? coreutils? Or try and come up with some higher level critera? Perhaps instead of trying to keep such a page fully up to date and list everything we could phrase it as: "Fedora Infrastructure would like to thank the following projects for their software" Thoughts?

Mhm, perhaps we can say

Fedora Infrastructure would like to thank the following open-source projects for their work: [text list here]

Fedora Project also proudly uses the following FOSS software:

[... kernel, etc ...]

I think we could start by creating a list of fedora-infra FOSS tools, then start populating a list of other FOSS software used in fedora.

If all looks good, we can create a page and link it to the sponsors page, or we may be able to put a text list, if the paid sponsors are okay with that.

Mhm, perhaps we can say Fedora Infrastructure would like to thank the following open-source projects for their work: [text list here] Fedora Project also proudly uses the following FOSS software: [... kernel, etc ...] I think we could start by creating a list of fedora-infra FOSS tools, then start populating a list of other FOSS software used in fedora. If all looks good, we can create a page and link it to the sponsors page, or we may be able to put a text list, if the paid sponsors are okay with that.
attachment [0001-Give-credit-to-FOSS-projects-infra-ticket-506.patch](/fedora-infrastructure/issue/raw/files/3eb3e799a82faf55affc77a03f0ff2590b1e8c1988fa853adac6770936a87ea2-0001-Give-credit-to-FOSS-projects-infra-ticket-506.patch)

Patch applied and i18n added. Maybe we can update the list, depending on how deep we want to get.

Thank you.

Patch applied and i18n added. Maybe we can update the list, depending on how deep we want to get. Thank you.
Sign in to join this conversation.
No milestone
No project
No assignees
7 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
infra/tickets#506
No description provided.