removing dupplicate teams at transifex
by Kévin Raymond
Hi there,
Months ago we merged the dupplicate teams at transifex.net.
I had to remove the old teams, but still haven't done that yet.
I saw some push on the wrong teams...
Therefore, I plan to remove those teams (without any team member) next week.
I have to do them all one by one, not sure if I will have all the access but
will sort this.
You should not notice any thing unless you were pulling the wrong language code.
Which should not happen if you have the right language mapping:
https://fedoraproject.org/wiki/Setting_up_a_document_with_Transifex#Step_...
Please tell me if you think something has to be done before.
I will probably pull them all for backup but since I haven't started.. :)
See ya!
--
Kévin Raymond
(Shaiton)
11 years
Documenting Features
by Pete Travis
Hey guys,
I've been reading the Feature discussions on devel@ today, and an idea
came to mind. A process for documenting accepted Features would help
prevent major changes from slipping through the cracks. Here's what I
came up with so far; I think we can hammer it into something useful:
Accepted Features[1] will be listed in a table roughly analogous to that
used for Release Note Beats[2]. The table would have columns for the
Feature name, a docs volunteer, and developer contact, as well as others
reflecting the Feature documenting workflow.
A set of guidelines for the docs volunteer covering a feature will come
along with the table. The set of tasks to be juggled might include:
- Establishing an appropriate developer point of contact to aid in
documentation. Note that this isn't always the feature owner.
- Ensuring the content of the Feature is understandable by a
hypothetical average user.
- Working up a basic guide to implementing the feature, if applicable.
- Creating an entry for the Feature in the appropriate Release Notes
beat.
- Checking existing guides for impact caused by the new Feature, filing
bugs as needed, and assisting the guide owners in updating as
appropriate.
A defined process like this will help split up the workload caused by
feature churn and cut redundant efforts by providing new information for
multiple published works. Your thoughts?
[1]
http://fedoraproject.org/wiki/Releases/19/FeatureList#Fedora_19_Accepted_...
[2] http://fedoraproject.org/wiki/Category:Documentation_beats
--
-- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
11 years
Sponsorship logo(s) for docs.fedoraproject.org
by Steve Gordon
Hi all,
It's been brought to our attention [1] that unlike much of fedora's web presence the docs site doesn't currently list a hosting sponsor. If you look at fedoraproject.org this is the entity that is listed under "Hosting Sponsor" on the right hand side bar (if you CTRL+R a few times you will also see that it changes on each load depending on where the content ends up being served up from).
We discussed this in the docs meeting today and it seems like what is required is injection of some additional JavaScript into the publican-fedora brand and some HTML to use it in the side bar. There are potentially some issues with where that JavaScript comes from based on the responses from the web team on the bug but before proceeding any further those of us at the meeting just wanted to check if there were any objections to doing this?
Thanks,
Steve
[1] https://bugzilla.redhat.com/show_bug.cgi?id=611891
11 years
Self-Introduction: Navneet Singh
by Navneet Singh
Hi everyone,
I am Navneet Kumar Singh, a second year undergraduating B.Tech Computer
Science Engineering Student from Jodhpur Institute of Engineering and
Technology, Jodhpur, Rajasthan, India.
I live in Jodhpur, Rajasthan, India ( GMT+5:30). My FAS account username is
"navneetsingh0693" and my IRC nickname is "ns0693".
I learned about Fedora Documentation Team from Fedora Wiki only, and i am
interested in writing some help documentation for fedora as it will easier
to start my contribution in Fedora and gain more experience.
I have also applied for Fedora Ambassadors. I picked up documentation
because it helps other new users and students easier to grab use of Linux
and related stuffs and spread knowledge about it.
I have not contributed in my writings to any such project Fedora but i have
written many articles in schools and have a habit of writing about
everything i see new. I am having good amount of Computer Skills including
MS Office and Libre Office as Software Packages, C/C++ as Languages,
Linux/Windows as Platforms.
I am a very enthusiastic person interested much in contributing in FOSS
projects and chose Fedora as i love it.
GPG Key :
pub 2048R/3F045901 2013-02-25
Key fingerprint = E2D1 3061 56E4 6913 683F 7E21 22B7 5209 3F04 5901
uid Navneet Kumar Singh (IRC : ns0693, FAS :
navneetsingh0693) <navneetsingh0693(a)gmail.com>
sub 2048R/5F93A4D1 2013-02-25
So, i request everyone to help me out in getting started.
Thanks,
Navneet Singh
11 years, 1 month
Self-Introduction: Navneet Singh
by Navneet Singh
Hi everyone,
I am Navneet Kumar Singh, a second year undergraduating B.Tech Computer
Science Engineering Student from Jodhpur Institute of Engineering and
Technology, Jodhpur, Rajasthan, India.
I live in Jodhpur, Rajasthan, India ( GMT+5:30). My FAS account username is
"navneetsingh0693" and my IRC nickname is "ns0693".
I learned about Fedora Documentation Team from Fedora Wiki only, and i am
interested in writing some help documentation for fedora as it will easier
to start my contribution in Fedora and gain more experience.
I have also applied for Fedora Ambassadors. I picked up documentation
because it helps other new users and students easier to grab use of Linux
and related stuffs and spread knowledge about it.
So, i request everyone to help me out in getting started.
Thanks,
Navneet Singh
11 years, 1 month
Fedora Docs Meeting - 18 Feb 2013 1400 UTC
by Pete Travis
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Fedora Documentation Project - that's you - are meeting soon in #fedora-
meeting on freenode. The agenda is up at
https://fedoraproject.org/wiki/Docs_Project_meetings#18_February_2013, and the
meeting starts at 1400 UTC. Coffee and snacks are self-serve.
- -- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQEcBAEBAgAGBQJRKwgnAAoJEL1wZM0+jj2ZW4kIAI2tOo6n3IPYvnB2ku0MmxxT
+T6PZXHfPCrO29llNZ4805GCGbFH1vyg/urt3bSSkHIEWiU8oIPt7CBYb+0JzJaB
FDEM1Choa3TLaV7BYC6iuUmFdh3gbzwkW6y32z9Vqswu2C2HLCTPPHq4zNZCJNfo
z5mAFWtCCoynugEnHwK4Xfqe9tA9AiXsqtaL+tWqATGKiE361FSY3dfERNT8RZtL
3fKItMb2/rPXIpP5tZQ5uvH53NwEc9fQCgYPMsetlSw983uMpP8EHwqKGh4+5DfV
Sqw7aYKspinlDXabIIqhbfKTZKdEpP1BVjW68QubaXMO1LrBqbAxATpY0LLJZFU=
=qvKM
-----END PGP SIGNATURE-----
11 years, 1 month
Open Help Conference & Sprints 2013
by Shaun McCance
Hi all,
I'm hosting the Open Help Conference & Sprints again this year
on June 15-19 in Cincinnati, Ohio, USA.
http://openhelpconference.com/
The first two days are the conference portion. Abut half the
time is devoted to presentations, with the rest used for open,
attendee-led discussion. This format provides some structure,
but still lets everybody share their experiences.
On June 17-19, multiple open source documentation teams have
documentation sprints. This year I have four rooms of various
sizes, centered around a common break area. Sprints are great
for building communities and putting focus on a project.
Florian Nadge joined us last year. I'd love to see a group of
Fedorans come out to the conference or sprints this year.
Let me know if you have any questions.
Thanks,
Shaun
11 years, 1 month
Docs project meeting minutes - 18 Feb 2013
by Pete Travis
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
We had a meeting today, here's what happened:
- - Sparks, rudi, and releng are working out a new publishing system for us.
Sparks is showing admirable patience in responding to questions from the
group, thanks.
- - We would benefit from more involvement in beats writing
- - Sparks wants to use some of the bug time in the meeting to discuss
individual bugs filed against docs in general, and that meetings be used to
assign bugs that are currently tasked to the group. There was a murmur of
agreement, but the next topic unfortunately hijacked the group before we could
discuss the bug he quoted. Sorry, Sparks, my bad.
- - I'm going to change the default qa contact for all docs bugs to the docs-qa
mailing list. Anyone that wants to do QA should take ownership of the bug, and
anyone that wants direct assignment for QA should mail the list to discuss.
- - I'm going to directly contact all default assignee contacts for docs bugs
and remove anyone that is not responsive.
- - Since we are expecting more involvement in QAing bugs, we should make sure
the docs QA wiki pages make sense. Some concerns were expressed about the QA
process, and may be expressed on the list sometime soon.
http://fedoraproject.org/wiki/Docs_QA
http://fedoraproject.org/wiki/Docs_QA_Procedure
At a glance, I see that we'd substitute the signing up for qa contact for a
guide with instructions on finding ON_QA bugs in our docs, and perhaps more
changes. Participation welcome.
- -- If you aren't already, please subscribe to the docs-qa mailing list.
https://admin.fedoraproject.org/mailman/listinfo/docs-qa
And, here's the summary:
http://meetbot.fedoraproject.org/fedora-meeting/2013-02-18/fedora-
meeting.2013-02-18-14.00.log.txt
http://meetbot.fedoraproject.org/fedora-
meeting/2013-02-18/fedora_docs.2013-02-18-14.00.html
http://meetbot.fedoraproject.org/fedora-
meeting/2013-02-18/fedora_docs.2013-02-18-14.00.log.html
http://meetbot.fedoraproject.org/fedora-
meeting/2013-02-18/fedora_docs.2013-02-18-14.00.log.txt
http://meetbot.fedoraproject.org/fedora-
meeting/2013-02-18/fedora_docs.2013-02-18-14.00.txt
===================================================================================================
#fedora-meeting: Docs Project Meeting - Agenda:
http://fedoraproject.org/wiki/Docs_Project_meetings
===================================================================================================
Meeting started by randomuser` at 14:00:08 UTC. The full logs are
available at
http://meetbot.fedoraproject.org/fedora-
meeting/2013-02-18/fedora_docs.2013-02-18-14.00.log.html
.
Meeting summary
- ---------------
* roll call (randomuser`, 14:00:26)
* Follow up on action items (randomuser`, 14:05:46)
* no left over action items (randomuser`, 14:06:25)
* Docs Infrastructure (randomuser`, 14:06:49)
* LINK: https://fedorahosted.org/rel-eng/ticket/5214 (randomuser`,
14:10:32)
* Sparks to investigate further (randomuser`, 14:10:43)
* beat assignments (randomuser`, 14:21:39)
* more beat writers would be nice (randomuser`, 14:28:17)
* Outstanding BZ tickets (randomuser`, 14:28:32)
* LINK: http://tinyurl.com/lbrq84 (randomuser`, 14:28:52)
* doc-publican-rpm needs testing! (randomuser`, 14:32:09)
* LINK: http://jjmcd.fedorapeople.org/Download/doc-publican-rpm/
(jjmcd, 14:33:01)
* LINK: http://tinyurl.com/agh4mg6 (Sparks, 14:36:38)
* anyone with concerns on docs process should mail the docs list about
it (randomuser`, 15:02:04)
* Free Play (randomuser`, 15:02:13)
Meeting ended at 15:08:03 UTC.
Action Items
- ------------
Action Items, by person
- -----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
- ---------------------------
* randomuser` (76)
* Sparks (30)
* pkovar (24)
* jjmcd (15)
* zodbot (4)
* quaid (3)
* bcotton (3)
* Capesteve (3)
* Akash (2)
* nb (1)
* LoKoMurdoK (1)
* sparks (0)
Generated by `MeetBot`_ 0.1.4
- --
- -- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQEcBAEBAgAGBQJRIk0gAAoJEL1wZM0+jj2Z31MH/R13Hn1TpZz58twrDOmVjgVX
z1ydXg+/r4BK3OtVLK0vMKLj27PebYsCdgx0gGH+1t6A1CSeUcskc16vCeyHEcJE
0PvFYcuTB+baOeOQmstJ08Ou2swW27NoMoiQ8phZH32NvWeTyoQgBKHLsA4Bi+jU
0HBi3q8+DzToma4glA+Z3HvqFdPNYBQ4cAv/D6XWFIDHO5s61H6Rk5fOEg/ZwQoI
nZzGfrwpxvVYtJbrE+lmC4ZEfer2scmUitE4nyrBAg8ZsK7niNPL1dN8hJ2Ig4pt
GIQ9yKlenqE5oX7CkTCbLkdgciPfWYSrZaLViifHyy5tR4ZirHJofXyb8nF4l0U=
=aHZO
-----END PGP SIGNATURE-----
11 years, 1 month
Docs Project Meeting Summary
by Pete Travis
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
There were some technical issues at the start of today's meeting, so the logs
will be incomplete. I've pasted the log directly from my client in addition to
the logs captured by meetbot.
Minutes: http://meetbot.fedoraproject.org/fedora-
meeting/2013-02-11/fedora_docs_https:fedoraproject.orgwikidocs_project_meetings.2013-02-11-14.22.html
Minutes (text): http://meetbot.fedoraproject.org/fedora-
meeting/2013-02-11/fedora_docs_https:fedoraproject.orgwikidocs_project_meetings.2013-02-11-14.22.txt
Log: http://meetbot.fedoraproject.org/fedora-
meeting/2013-02-11/fedora_docs_https:fedoraproject.orgwikidocs_project_meetings.2013-02-11-14.22.log.html
- ----------------------------------------------------------------------------------------------
<Sparks> randomuser`: Meeting?
* tjikkun_work (~tjikkun@2a00:d10:2:1:a6ba:dbff:fef3:f431) has joined
<Sparks> #startmeeting Docs Project Meeting - Agenda:
https://fedoraproject.org/wiki/Docs_Project_meetings
<nirik> alas, we are working on zodbot. ;(
<puiterwijk> Sparks: meetbot is currently unavailable yet. I'm looking at it
now with Kevin
<Sparks> puiterwijk: Ya
<Sparks> #meetingname Fedora Docs
<Sparks> #topic Roll Call!
* Sparks is here
* Penguiniator is here (new member)
<randomuser`> sorry, distracted
* jreznik_ is now known as jreznik
* Sparks notes that nirik is working on zodbot and a git problem on
fedorahosted at the moment.
* pkovar is here
* Sparks hands the meeting over to randomuser`
<randomuser`> thanks, Sparks
<randomuser`> we'll wait a moment more for roll call
* bcotton (~bcotton(a)sheldon.rcac.purdue.edu) has joined
<randomuser`> #topic Follow up on last week's action items
<bcotton> hey randomuser` did you #startmeeting?
<randomuser`> bcotton, zodbot is MIA
* UnCleJack is here
<randomuser`> i'll have to do it manually
* threebean checks in #fedora-admin about zodbot
<bcotton> randomuser`: ah, okay. Good luck! (RIP Zodbot)
<puiterwijk> threebean: me and Kevin are working on it in -noc
<Sparks> threebean: They know
<randomuser`> I sent out a big pile of nag emails re: beats last night, and
responses are already trickling in
<threebean> puiterwijk: I see that now.. I just wandered in ;)
<randomuser`> Sparks, you were following up with infra?
<Sparks> Umm
<Sparks> randomuser`: For the Koji tag?
<randomuser`> "Sparks to follow up with RELENG on the additional repo and tags
in Koji"
<randomuser`> yeah
<randomuser`> #info
https://fedoraproject.org/wiki/Docs_Project_meetings#11_February_2013
<Sparks> I checked with Dennis and he was going to get back with me but had a
day off last week so I kinda missed him, I think.
<Sparks> I think he said he has created the tag and the repo and was testing
some things.
<Sparks> EOF
<randomuser`> okay, thanks
<randomuser`> I saw rudi is working on publican 3 for us,
http://lists.fedoraproject.org/pipermail/docs/2013-February/014825.html
* mmello (~Marcelo(a)186.215.54.218) has joined
<Sparks> Yes! Shouldn't be long now!
<randomuser`> Sparks, I can take the weekly nagging off the agenda if you'd
like to bring it up when appropriate
<Sparks> Sure, just create a topic for it as this will live for another few
weeks.
<randomuser`> will do, thanks
<randomuser`> #topic New Contributors
<randomuser`> I'd like to welcome Penguiniator and UnCleJack to the group
<Penguiniator> randomuser`, thanks
<UnCleJack> :-) thanks
<randomuser`> We're around if you have any questions, of course
* jduncan (~jduncan(a)pool-71-176-228-243.rcmdva.fios.verizon.net) has joined
<Sparks> Woot! Fresh meat!
<randomuser`> I mentioned a bacon chocolate cupcake recruiting bounty on the
list a while ago, and I plan on claiming it as their sponsor
<lnovich> randomuser - all yours
<UnCleJack> well, ive talked to Sparks about contributing to the security
guide, and told him i'll work on it on the weekend, but turns out i just need
some more time getting used to docbook & wrokflow, before i'm of any use
* movl has quit (Read error: No route to host)
<randomuser`> I think the best approach to start is to write it out, and worry
about the markup after
<Sparks> UnCleJack: If you make changes and send them to me in a patch I'll fix
the DocBook. :)
<UnCleJack> Sparks, That would be great :-D
<randomuser`> okay, enough picking on the new guys
<UnCleJack> Sparks, but please let me know what i did wrong, so i can learn
and send quality patches ;-)
<Sparks> UnCleJack: Content is the hard part. Tags are easy once you get use
to them.
* dwmw2_gone is now known as dwmw2
<Sparks> UnCleJack: Oh, I won't hold back. :)
* mdomsch (~mdomsch(a)cpe-70-116-14-133.austin.res.rr.com) has joined
<UnCleJack> Sparks, just the way i like it ;-O
<lnovich> i think getting content is the hard part as you can't just make this
all up
<chuckf> randomuser`: would you like me to see if I can get my meetbot to run
in here for the meeting?
<chuckf> or is it too late?
<Sparks> lnovich: Have you read the Security Guide? Clearly I can make up a
lot of stuff.
* zodbot (supybot@fedora/bot/zodbot) has joined
<randomuser`> chuckf, I think it's a moot point at this stage
<Sparks> chuckf: I think we've been using the tags for zodbot so maybe if we
run the logs through it will make the minutes?
<chuckf> randomuser`: okay
- --
- -- Pete Travis
- Fedora Docs Project Leader
- 'randomuser' on freenode
- immanetize(a)fedoraproject.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
iQEcBAEBAgAGBQJRGQmqAAoJEL1wZM0+jj2ZFxoH/RjtVsXvrC8SUflEeWwkHapQ
mRUEztOsxu2EEw4a7GjU8LdZnsZ/FM5DvuffBDSO7tgFH2lQ4qBx5KZq1SzL1AZ1
aopm/WDSHTjJvVUPIuqdiimcIlUtQGNydOvu+1il3nSBk7u0BR/YFIdsZHS7dxKC
KI09e/WK+8G9evUwUHZGQrqYLNr16uQcvTnG3Px+uLHpvAeoc71GW9tWNdwyUaSO
1rKWwYEwnQ2NPuxrE/x8BBrnd4+4V/qlZ64mCxsC9qthkFB+52XM764hgeCq5uxf
u4JuUyvj90y+FXbApGVWY4C5rSl+RGqDiK8wxPSCuS/EAZunzfkhlf4E2RBfjeE=
=H5wS
-----END PGP SIGNATURE-----
11 years, 1 month