Re: [Fedora Release Notes] #13: Convert content from wiki Beats to XML (scripted)
by fedora-badges
#13: Convert content from wiki Beats to XML (scripted)
--------------------+-------------------------------------------------------
Reporter: quaid | Owner: quaid
Type: task | Status: closed
Priority: major | Milestone: PR-ready
Component: Admin | Version:
Resolution: fixed | Keywords:
--------------------+-------------------------------------------------------
Changes (by quaid):
* status: new => closed
* resolution: => fixed
Comment:
This worked out OK, about as well as the Moin Moin stuff with slightly
better consistency and the XML was not broken out of the conversion box.
Still a PITA to do the conversion after. Need to look in to starting a
new part of fedora-doc-utils to do more automagic, based on our experience
here.
--
Ticket URL: <https://fedorahosted.org/release-notes/ticket/13#comment:3>
Fedora Release Notes <https://fedorahosted.org/release-notes/>
Fedora Release Notes
15 years, 5 months
Re: [Fedora Release Notes] #24: Any fixes needed to f-r-n for RC ready (potential blockers)
by fedora-badges
#24: Any fixes needed to f-r-n for RC ready (potential blockers)
-----------------------+----------------------------------------------------
Reporter: quaid | Owner: quaid
Type: task | Status: new
Priority: critical | Milestone:
Component: Admin | Version:
Resolution: | Keywords:
-----------------------+----------------------------------------------------
Changes (by quaid):
* summary: RC fix management (if required) => Any fixes needed to f-r-n
for RC ready (potential blockers)
Comment:
You and me brother! I can only claim that it made sense at the time ...
I think this is a just-in-case blocker. Looking at the order of what
tickets were made, I think this task is specifically for fixing problems
in the f-r-n package before final push to Release Candidate. That wasn't
specifically called out in other tickets; e.g. "check PO files from L10n"
doesn't cover all aspects of what might break or need fixing. We may also
get emergency, must-be-in-notes content that has to go in, which is
something else that might need "fixing".
--
Ticket URL: <https://fedorahosted.org/release-notes/ticket/24#comment:2>
Fedora Release Notes <https://fedorahosted.org/release-notes/>
Fedora Release Notes
15 years, 5 months
[kwade@redhat.com: fedora-release-notes PO files updated for F10 GA]
by Karsten Wade
FYI ...
Anyone who wants to help triage questions from translators, please
join fedora-trans-list.
Often questions arise about specific words, usage, and terms in
English. It is very informative for learning about how to write to be
translated.
----- Forwarded message from Karsten 'quaid' Wade <kwade(a)redhat.com> -----
Date: Fri, 7 Nov 2008 04:46:28 -0800
From: Karsten 'quaid' Wade <kwade(a)redhat.com>
To: fedora-trans-list(a)redhat.com
Subject: fedora-release-notes PO files updated for F10 GA
X-BeenThere: fedora-trans-list(a)redhat.com
The following modules POT/PO files have been modified for F10. These
are the final changes for this content for the Fedora 10 release.
Thank you for your patience as we worked through this past deadline.
We were able to go over all the content one more time, fix a number of
small errors, update with changes from the wiki, and close a small
number of bug reports.
release-notes
readme-burning-isos
about-fedora
These modules are _not_ complete yet, but are being actively worked
on. In particular, the 'readme' file requires a complete rewrite.
These should be ready within the next few hours:
readme
readme-live-image
Happy translating!
Questions or problems? Ask on this list or file a bug report:
http://tinyurl.com/nej3u
Thanks,
- Karsten
--
Karsten 'quaid' Wade, Community Gardener
http://quaid.fedorapeople.org
AD0E0C41
--
Fedora-trans-list mailing list
Fedora-trans-list(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-trans-list
----- End forwarded message -----
--
Karsten 'quaid' Wade, Community Gardener
http://quaid.fedorapeople.org
AD0E0C41
15 years, 5 months
Seeking for legal advice (fedora-zh.org)
by Yuan Yijun
Hi,
We some ambassadors are setting up another website for fedora (will be
http://{bbs,wiki,news}.fedora-zh.org ). Current copyright and licese
rules:
* any contents belong to its author
* on bbs any original contents must be licensed under OPL + CC(by-sa)
* on news any original contents must be licensed under CC(by-sa)
* on wiki all contents are in public domain
What I want to know is:
* should we ask the authors to assign copyright ownership to our
organization? but we do not have an organization yet, and we don't
have the effort of setting up a CLA (!) system.
* the reason to use OPL is that I hope some content can be transfered
to fedoraproject wiki without asking for more permission. Is it
possible if we do not own those contents?
* the reason to use CC(by-sa) is that the license is so popular. It
seems fedoraproject suggests some contents to be CC-ed (artwork,
videos) except for documents, why?
* is there any conflict in our requirement that contents are licensed
in both OPL and CC(by-sa)?
* any other problems do you think?
Thanks!
--
bbbush ^_^
15 years, 5 months
FDSCo Meeting 2008-11-05 Summary
by Karsten Wade
== Attendees ==
* David Nalley (ke4qqq
* Paul W. Frields (stickster)
* Karsten Wade (quaid)
== Summary & Actions ==
=== Actions ===
* ACTION: Wed, Thu #fedora-docs focused on beat -> XML for relnotes
* ACTION: IG all day on #fedora-docs Thu, Fri
* ACTION: CMS hunt to proceed according to this plan:
1. We make a big public splash that we are hunting hard
2. Talk lots on f-docs-l for a week and pick a shortlist
3. Announce that shortlist and that we are actively trying
things out; put up test instances, give test drives
4. Amongst that, we mention (again) that we need actual talent
to deliver the solution within Fedora, and invite those folks to join
the discussion and help us with the decision process.
5. Ideally we get both a decision and a doer at the same time
6. Optionally we discover we aren't going to get it
that easy, but we do get a shortlist or a single choice; then we can
decide if we want to troll with the shortlist.
=== Summary ===
* Post-F10 relnotes and schedule analysis notes:
** Once Beats are converted to XML, the XML is canonical _for_that_release_
** Should we move back to a packaged fedora-release-notes for Beta?
*** Package for Preview Release gets only a few days in the wild
before we have to freeze for l10n
*** Could sync with the development freeze between Beta and PR
** How do we want to handle corrections to Beats after conversion to
XML?
*** Do we freeze wiki changes from there, work only in XML, and use BZ
or Trac to gather fix-it requests?
*** Two-way sync is a PITA
*** If a package, they can file bug reports for a clear path
** Need to ponder more on what to do next time
* Hoping search for CMS brings in new contributors to Docs/Fedora,
rather than stretching existing ones thinner
** Publicity on CMS project might help here; perhaps paid $CMS
developers might help for the "Fedora Documentation chooses $CMS"
publicity.
--
Karsten 'quaid' Wade, Community Gardener
http://quaid.fedorapeople.org
AD0E0C41
15 years, 5 months
