Re: Fedora 7 Test 1 Release Notes
by Paul W. Frields
On Mon, 2007-02-12 at 12:19 -0500, Will Woods wrote:
> On Fri, 2007-02-09 at 22:06 -0500, Paul W. Frields wrote:
> > Fedora 7 Test 1 Release Notes
> > ==============================
>
> Dude, this is *awesome*. What can I do to help make sure updated release
> notes appear alongside Test2?
Glad you asked! :-) Simply pitch in by editing the Wiki
"beats" (subject matter areas) for the Release Notes, or in any of the
five other ways we've helpfully set up to collect content:
http://fedoraproject.org/wiki/DocsProject/ReleaseNotes/Process
We will be condensing content down to a one-sheet for test2 again, but
for test3, there will be a full load of content going to L10N for
translation. The updates between test3 => final are usually minimal,
thus the release notes change little as well. So if they start
translating in advance of test 3 (14+ days), even if a language isn't
finished in time for test3, it will have plenty of time to get there for
the final release.
--
Paul W. Frields, RHCE http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
Fedora Project Board: http://fedoraproject.org/wiki/Board
Fedora Docs Project: http://fedoraproject.org/wiki/DocsProject
17 years, 2 months
how to subscribe to the release notes feed
by Karsten Wade
A reminder to all that this mailing list ...
http://www.redhat.com/mailman/listinfo/fedora-relnotes-content
is the feed for all release notes content coming from:
* Change reports from Docs/Beats/
* Bugzilla reports assigned/Cc:'d/flagged for relnotes(a)fedoraproject.org
* Usage of *docs* in CVS commit logs
* Direct relnotes(a)fp.o email
This list is the way to turn on/off the feed of release notes content.
If you are writing a release notes beat, you must be subscribed to this
list. This is how you are aware of incoming content submissions.
cheers - Karsten
--
Karsten Wade, RHCE, 108 Editor ^ Fedora Documentation Project
Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject
quaid.108.redhat.com | gpg key: AD0E0C41
////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
17 years, 2 months
Fedora 7 Test 1 and release notes
by Rahul Sundaram
Hi
Some strong notes here:
http://distrowatch.com/weekly.php?issue=20070205#news
A followup comment #72 by the author (CC'ed) reveals that the primary
concern is over lack of release notes.
http://distrowatch.com/weekly.php?issue=20070205&mode=16#comments
Of course with our level of resources doing full fledged releases notes
and translation for a test 1 release of a fast moving distribution like
Fedora is not easily done. I was traveling to FUDCon Boston 2007
finalized and unfortunately didnt have any time to work on the release
notes but this shouldnt be resting on me entirely. However a single page
overview or some notes within the announcements itself wouldnt take much
time.
It would also be good to link to our QA efforts and release process like
http://fedoraproject.org/wiki/QA/7/Test1TreeTesting to avoid the
impressions of a lack minute rush up job. The more transparent we are
with our development efforts, the better we would be at avoiding
misconceptions.
Rahul
17 years, 2 months
Re: Fedora 7 Test 1 and release notes
by Rahul Sundaram
Jesse Keating wrote:
> On Friday 09 February 2007 10:15, Rahul Sundaram wrote:
>> When you are composing the spin and doing the release announcement, it
>> is easy enough to just point out the major changes.
>>
>> Say GNOME KDE and Kernel x.y. Important feature z etc.
>
> I don't always know this information, and it's just as much of a pain in the
> ass for me to go looking for it as it is for you.
Which is why I said that individual developers need to be more proactive
on passing on important upstream as well as Fedora specific changes. Any
single person doing it is going to be painful.
> Incorrect. Test1 serves as a somewhat stable starting point for fleshing out
> the features that are planned for the next release. Especially if we wind up
> doing hackfests just after Test1 continually. A lot of the features aren't
> really suitable for testing by anybody other than the developer, but they
> need something they can install with their changes that actually installs
> rather than the more often than not broken rawhide repo at this stage. Test1
> provides them a platform to put their package on and continue to develop it.
> Often times the feature isn't baked enough so that anybody else looking at it
> would do any good.
I think we are aiming at a different audience for each of the test
releases. We need to agree on and pass on that to the wider folks involved.
Rahul
17 years, 2 months
Re: Fedora 7 Test 1 and release notes
by Rahul Sundaram
Jesse Keating wrote:
> On Friday 09 February 2007 05:33, Rahul Sundaram wrote:
>> It wouldnt have taken more than a few minutes for the developers
>> involved to quickly note what major changes were pushed into the test 1
>> releases, what we tested, known bugs etc on a single page. No
>> translation required.
>
> Would you like to be on the hook for this?
No. I have done the work before because the people who would doing the
package changes didnt bother conveying the release notes worthy
information. It is very inefficient for me to go through individual
package changelogs for thousands of packages to hope and find useful
information. In many cases upstream does the changes so they are not
even noted in the changelog. The only way this would scale is for
individual developers to get involved better.
When you are composing the spin and doing the release announcement, it
is easy enough to just point out the major changes.
Say GNOME KDE and Kernel x.y. Important feature z etc.
Test1 is almost always a mixed bag
> of random crud that has creeped into rawhide. It's just a snapshot of what
> has been doing on, and in no way is it supposed to be a demo of any of the
> planned features. Almost any feature that shows up in Test1 is going to be
> half baked and perhaps not in a desired state to document or even draw
> attention to.
If we want folks to actually test them we need to point to draw them in
by pointing out the changes that we do. If there is nothing worth
pointing out, test 1 isnt useful.
>
> We have what we tested and known bugs on one page, the TreeTesting wiki page.
We should included that within the announcement too.
Rahul
17 years, 2 months
Self-Introduction: Maxim Dziumanenko
by Maxim V. Dziumanenko
Hello everybody!
Full legal name: Maxim V. Dziumanenko
City, Country: Kyiv, Ukraine
Profession: RedHat technical support service
Company: Softprom Ltd.
Goals in the Fedora Project
I want to maintain Ukrainian translation of Fedora documentation.
Historical qualifications
What other projects or writing have you worked on in the past?
I'm coordinator of Ukrainian translation of GNOME, maintainer of
Ukrainian translation of RedHat tools, Ukrainian translation of XFCE and
Ukrainian translation of many programs in Translation Project.
Beside this I'm author of gedit-pomode plugin.
What level and type of computer skills do you have?
I have good Technical Support skills and programmings skills in
Python and C/C++.
What makes you an excellent match for the project?
I have huge experience in technical translation into the Ukrainian
language.
GPG KEYID and fingerprint
[mvd@fc6 ~]$ gpg --fingerprint 2E5A8871
pub 1024D/2E5A8871 2007-02-07
Key fingerprint = 5241 2A56 914D 6049 7C10 B29A CB26 58A3 2E5A
8871
uid Maxim V. Dziumanenko <dziumanenko(a)gmail.com>
sub 1024g/CBDA049C 2007-02-07
Best regards
--
Maxim V. Dziumanenko <dziumanenko(a)gmail.com>
17 years, 2 months
Seeking clarification on the FDSCo Elections
by John Babich
FDP Team Members:
I appreciate that FUDCon 2007 is starting in Boston today. I wish I could
be there, but I still plan to attend via IRC and any blogging being done. It
should be a great time for all.
Although this is a very busy time, we need to clear up a few confusing issues
regarding the FDSCo elections.
I am referring to three documents:
1. "Nominations now open, Elections for FDSCo 2-Feb to 12-Feb",
https://www.redhat.com/archives/fedora-docs-list/2007-January/msg00045.html
2. http://fedoraproject.org/wiki/DocsProject/Policy/FDSCoElections
3. http://fedoraproject.org/wiki/DocsProject/SteeringCommittee/Nominations
First of all, full disclosure: I am a candidate for this election. :-)
This is how I understand the election based on these documents:
1. All 7 seats on the FDSCo are open for re-election (as stated in doc #1).
2. Therefore, each qualified voter gets up to 7 votes, 0-7 of which are
cast for each candidate. For example, I can cast all 7 votes for one
candidate, or distribute them how I please among all the candidates,
as long as I do not exceed 7 votes cast (stated in doc #2).
Implicit in this
is that a candidate can vote for one's self.
3. I cannot vote for someone who has not self-nominated on the Nominations
page (doc #2).
4. If 7 seats are open, 9 candidates must self-nominate (doc #2).
5. According to doc #2, the deadline for self-nomination is passed (3 days
before 2 Feb is 30 January).
6. Consequently, there are now only 4 candidates, including myself, as of
the time of this writing (doc #3).
7. According to doc #2, the voting is therefore automatically postponed one
week from 2 February, making the new date 9 February for the election.
8. This is in the hope that 5 more candidates will self-nominate by by placing
their own names on doc #3.
9. If there are still less than 7 candidates, then voting will take
place with the
number of candidates posted (doc #2).
Now, please clarify the following points:
1. Since we are a global community, are we referring to these dates as
beginning on 12:01 AM (0001 hours) UTC (also known as GMT) or by
another standard? In other words, will voting now take place on 9 Feb
at 12:01 (0001 hours) UTC?
2. WIll the next wave of self-nominations close on 6 February or 9 February?
It may be fortunate that the voting period was extended automatically, so that
we have the opportunity to clarify these points. I'm sorry that I
didn't grasp the
situation right away as I am very busy at work at the moment.
Once these decisions are taken regarding this election, I further suggest that
we post them prominently on the nominations page, along the lines of:
1. You have seven (7) votes.
2. You may cast anywhere from 0 to 7 votes in total.
3. Cast 0-7 votes for each candidate up to 7 votes.
etc.
Best Regards and Enjoy FUDCon,
John Babich
Volunteer, Fedora Docs Project
17 years, 2 months
FDSCo meeting for 06-Feb-2007
by Karsten Wade
We are in fact meeting today on #fedora-docs.
Anyone is welcome. Discussion is around:
* Fixing and continuing with our election situation
* FUDCon reports
* AOB
I don't have much to report back from FUDCon about FDP in particular,
but we might as well get it into the record. :) Paul may have more to
say.
If no one is available, I'll just use the time to figure out how to fix
our election situation.
- Karsten
17 years, 2 months
Feedback on Join the Fedora Community
by John Babich
Concerning "Join the Fedora Community"
http://www.fedoraproject.org/wiki/Join
Short version: I like it!
Long version:
The 6 categories (Content Developer, Designer, People Person,
OS Developer, Translator, Web Developer) really capture the roles
different people play in the Fedora Project.
It would be interesting to describe ourselves in terms of these roles.
I personally see myself as a Content Developer first, a Web Developer
second, with some People Person thrown in for good measure.
I also like the graphics. Maybe we can incorporate them into other pages.
The Docs Project is a natural place for the Content Provider graphic.
Kudos to Karsten and Mairin!
17 years, 2 months