UG?
by Jonathan Roberts
Hi all,
I was just wondering if anybody could give me some ideas about what
are the main tasks that need doing for the UG? Or is it that people
are just diving in and doing whatever?
Hopefully will have some more time to contribute a bit again over the
next week or so...fingers crossed!
Cheers,
Jon
16 years, 9 months
Re: problem while sending gpg key to mit key server
by Mustafa Qasim
Hello! All folks there. I need some help in completing my joining process. I
am stuck at the "Sending gpg key to mit key server" point. I am starting the
story from start because this time I am including some other group's address
in TO field.
I studied the Joining Check list page and perform the tasks given there.
1)Introduced my self a couple of days ago.
2) Created the ssh key
3) Created the gpg key
(Take a backup of both ~/.ssh and ~/.gnupg directories)
4) Created the Bugzilla account
5) Tried to sent the gpg key to mit server thjrough the command given in the
Check list
gpg --keyserver pgp.mit.edu --send-keys GPGKEYID
But at this stage it gives connection time out error. I went to
gpg.mit.edu through firefox and read that we can also submit the key
by pasting the ASCII of our key on their page. But i couldn't extract
the ASCII by the export command
gpg --export --armor alajal(a)gmail.com > mykey.txt
it returns
gpg: WARNING: nothing exported
So please help me to get out of this problem.
--
Mustafa Qasim
Lahore, Pakistan
Cell: 0321-6614972
URL: http://www.mustu.info
16 years, 9 months
FDSCo Meeting 2007-07-17 IRC log
by Karsten Wade
HTMl available at:
http://fedoraproject.org/wiki/DocsProject/SteeringCommittee/Meetings/Minu...
----
09:06 < quaid> <meeting>
09:06 < quaid> then we can discuss that :)
09:06 < quaid> http://fedoraproject.org/wiki/DocsProject/SteeringCommittee/Meetings#Agenda
09:07 < jmbuser> JohnBabich
09:07 < quaid> KarstenWade
09:07 < quaid> anyone else around? couf? glezos? Bob?
09:07 < quaid> many, quiet around here ...
09:09 < jmbuser> KC0WYC: ping
09:09 < quaid> jmbuser: so, what did you think? are you familiar with content workflows like that?
09:10 < jmbuser> quaid: Yes, I am
09:11 < jmbuser> quaid: I like most of it - I prefer to reserve staging for things waiting to be put into production
09:11 < jmbuser> quaid: I prefer calling it something else
09:12 < jmbuser> quaid: Similar to developing code in large shops
09:13 < jmbuser> quaid: test / staging / production for coding
09:13 < jmbuser> quaid: draft / CVS storage / published for docs... something like that
09:14 < jmbuser> quaid: Is that just semantics?
09:14 -!- EvilBob [n=bob(a)fedora/pdpc.sustaining.BobJensen] has joined #Fedora-Docs
09:15 < quaid> jmbuser: kind of
09:15 < jmbuser> quaid: Then, treat it accordingly :-)
09:15 < quaid> jmbuser: it might be Plone usage, in which case it is easier to accept than to reeducate at every turn
09:16 < quaid> at least, I got from daMaestro that it was plone language, but I could be wrong
09:16 < jmbuser> quaid: I can live with that
09:16 * quaid is glad that someone else who understands content workflows is doing a sanity check
09:17 < quaid> our point is to make it possible for 10x the people to be publishers, so it should all be easier in the end
09:17 < jmbuser> quaid: +1
09:17 < quaid> I think stickster_work made his points on list
09:19 -!- rlingk [n=devnull(a)pat1.orbitz.net] has joined #fedora-docs
09:20 * quaid finishes looking at the diagrams again
09:20 < quaid> I think we can push for a ratification on list
09:21 < jmbuser> quaid: What gives me hope is that someone who is a translator is working on it, so he gets it and takes it into account
09:23 < jmbuser> quaid: Not to diminish the contribution of us monolinguists
09:23 < quaid> hey, if this was any other part of Fedora, they'd probably forget l10n
09:23 < quaid> ok, email sent on that subject requesting final questions and/or ratification
09:24 < jmbuser> quaid: +1
09:24 < quaid> ok, on to the next item ..
09:24 < quaid> http://vpv.kapsi.fi/blog/2007/07/16/weekly-report-week-28/
09:25 < quaid> just to get vpv's report into the record :)
09:26 < vpv> I'm here. As you can see, there are some problems, but they should be manageable
09:26 < quaid> vpv: no worries, you seem to have it handled;
09:26 < quaid> vpv: are you getting the kind of responses you need on f-devel-l?
09:27 < quaid> I'm wondering if some tips about e.g. XMLRPC might be useful
09:28 < vpv> right now I really don't need thay much more than coding ;)
09:28 < quaid> yeah, that is a good call
09:28 < quaid> worry about performance later :)
09:28 < jmbuser> vpv: Do you have a way to parse "info" now?
09:29 < vpv> probably the only way to solve the XMLRPC slowness would be profiling, since the calls are correct and they work...
09:29 < vpv> jmbuser: the only way I've come up with is to download upstream sources from CVS
09:29 < vpv> or optionally from SRPM repos
09:30 < vpv> since I haven't found or there might not even be an info -> DocBook XML converter
09:30 * quaid doubts there is
09:30 < quaid> would probably make TeX fans roll over in their chairs
09:31 -!- rlingk [n=devnull(a)pat1.orbitz.net] has left #fedora-docs ["Leaving"]
09:32 < quaid> ok, then ...
09:33 < quaid> vpv: anything you can think that will make it _easier_ on you, let me know, I might be able to help :)
09:33 < quaid> moving on ...
09:33 < vpv> ok :)
09:33 < quaid> election planning ...
09:34 < quaid> just making sure we don't get behind there, I think we're ok
09:34 < quaid> that and guide talk ...
09:35 < quaid> jmbuser: with your limited availability, how can we have your time be able to help the other writers contribute/finish the DUG?
09:35 * quaid ponders this for himself _all_the_time_
09:36 < jmbuser> quaid: Were my tasks useful or should I break them down further?
09:36 < quaid> jmbuser: good question, let me look at them that way ...
09:38 < quaid> jmbuser: ok, seems reasonable for now
09:38 < quaid> jmbuser: maybe some more chatter on the list?
09:38 < quaid> people often have a "sudden few hours", are reading their lists, and if there is a fresh request, they are more likely to dive into it
09:38 < quaid> so, if the "tasks are updated, have at it" sits for a few weeks ...
09:39 < quaid> maybe people wonder if it is still happening? etc.
09:39 < jmbuser> quaid: I can post to the list and update my blog more often
09:39 < quaid> jmbuser: like I said, trying to think of, "If John only has 10 minutes for Fedora Docs today/this week/etc., what is a way he can have a bigger impact than e.g. editing a paragraph."
09:40 < jmbuser> quaid: Things are finally getting under control at work
09:40 < quaid> that's good
09:41 * quaid is going more out of control :)
09:41 < jmbuser> quaid: I would have to say that defining tasks and promoting greater participation...
09:41 < quaid> jmbuser: just a 'leadership thinking' idea I'm passing along, that's all; I often find myself doing something small and silly just to be doing something, and I try to remember to think of an overarching way I can make a difference.
09:42 < jmbuser> quaid: would be a good use of my time right now
09:42 < quaid> for example, if I didn't read that post but instead wrote up our minutes ...
09:42 < quaid> jmbuser: sounds great; let's find a way to make that chatter on the list, too
09:42 < quaid> ok, that's all of that for me
09:42 < quaid> anything else from anyone else?
09:43 < quaid> ok, closing the meeting in 30 seconds ...
09:44 -!- nman64 [n=n-man@fedora/nman64] has joined #fedora-docs
09:44 < jmbuser> +1
09:49 < quaid> </meeting>
16 years, 9 months
FDSCo Meeting YYYY-MM-DD IRC log
by Karsten Wade
HTMl available at:
http://fedoraproject.org/wiki/DocsProject/SteeringCommittee/Meetings/Minu...
----
09:06 < quaid> <meeting>
09:06 < quaid> then we can discuss that :)
09:06 < quaid> http://fedoraproject.org/wiki/DocsProject/SteeringCommittee/Meetings#Agenda
09:07 < jmbuser> JohnBabich
09:07 < quaid> KarstenWade
09:07 < quaid> anyone else around? couf? glezos? Bob?
09:07 < quaid> many, quiet around here ...
09:09 < jmbuser> KC0WYC: ping
09:09 < quaid> jmbuser: so, what did you think? are you familiar with content workflows like that?
09:10 < jmbuser> quaid: Yes, I am
09:11 < jmbuser> quaid: I like most of it - I prefer to reserve staging for things waiting to be put into production
09:11 < jmbuser> quaid: I prefer calling it something else
09:12 < jmbuser> quaid: Similar to developing code in large shops
09:13 < jmbuser> quaid: test / staging / production for coding
09:13 < jmbuser> quaid: draft / CVS storage / published for docs... something like that
09:14 < jmbuser> quaid: Is that just semantics?
09:14 -!- EvilBob [n=bob(a)fedora/pdpc.sustaining.BobJensen] has joined #Fedora-Docs
09:15 < quaid> jmbuser: kind of
09:15 < jmbuser> quaid: Then, treat it accordingly :-)
09:15 < quaid> jmbuser: it might be Plone usage, in which case it is easier to accept than to reeducate at every turn
09:16 < quaid> at least, I got from daMaestro that it was plone language, but I could be wrong
09:16 < jmbuser> quaid: I can live with that
09:16 * quaid is glad that someone else who understands content workflows is doing a sanity check
09:17 < quaid> our point is to make it possible for 10x the people to be publishers, so it should all be easier in the end
09:17 < jmbuser> quaid: +1
09:17 < quaid> I think stickster_work made his points on list
09:19 -!- rlingk [n=devnull(a)pat1.orbitz.net] has joined #fedora-docs
09:20 * quaid finishes looking at the diagrams again
09:20 < quaid> I think we can push for a ratification on list
09:21 < jmbuser> quaid: What gives me hope is that someone who is a translator is working on it, so he gets it and takes it into account
09:23 < jmbuser> quaid: Not to diminish the contribution of us monolinguists
09:23 < quaid> hey, if this was any other part of Fedora, they'd probably forget l10n
09:23 < quaid> ok, email sent on that subject requesting final questions and/or ratification
09:24 < jmbuser> quaid: +1
09:24 < quaid> ok, on to the next item ..
09:24 < quaid> http://vpv.kapsi.fi/blog/2007/07/16/weekly-report-week-28/
09:25 < quaid> just to get vpv's report into the record :)
09:26 < vpv> I'm here. As you can see, there are some problems, but they should be manageable
09:26 < quaid> vpv: no worries, you seem to have it handled;
09:26 < quaid> vpv: are you getting the kind of responses you need on f-devel-l?
09:27 < quaid> I'm wondering if some tips about e.g. XMLRPC might be useful
09:28 < vpv> right now I really don't need thay much more than coding ;)
09:28 < quaid> yeah, that is a good call
09:28 < quaid> worry about performance later :)
09:28 < jmbuser> vpv: Do you have a way to parse "info" now?
09:29 < vpv> probably the only way to solve the XMLRPC slowness would be profiling, since the calls are correct and they work...
09:29 < vpv> jmbuser: the only way I've come up with is to download upstream sources from CVS
09:29 < vpv> or optionally from SRPM repos
09:30 < vpv> since I haven't found or there might not even be an info -> DocBook XML converter
09:30 * quaid doubts there is
09:30 < quaid> would probably make TeX fans roll over in their chairs
09:31 -!- rlingk [n=devnull(a)pat1.orbitz.net] has left #fedora-docs ["Leaving"]
09:32 < quaid> ok, then ...
09:33 < quaid> vpv: anything you can think that will make it _easier_ on you, let me know, I might be able to help :)
09:33 < quaid> moving on ...
09:33 < vpv> ok :)
09:33 < quaid> election planning ...
09:34 < quaid> just making sure we don't get behind there, I think we're ok
09:34 < quaid> that and guide talk ...
09:35 < quaid> jmbuser: with your limited availability, how can we have your time be able to help the other writers contribute/finish the DUG?
09:35 * quaid ponders this for himself _all_the_time_
09:36 < jmbuser> quaid: Were my tasks useful or should I break them down further?
09:36 < quaid> jmbuser: good question, let me look at them that way ...
09:38 < quaid> jmbuser: ok, seems reasonable for now
09:38 < quaid> jmbuser: maybe some more chatter on the list?
09:38 < quaid> people often have a "sudden few hours", are reading their lists, and if there is a fresh request, they are more likely to dive into it
09:38 < quaid> so, if the "tasks are updated, have at it" sits for a few weeks ...
09:39 < quaid> maybe people wonder if it is still happening? etc.
09:39 < jmbuser> quaid: I can post to the list and update my blog more often
09:39 < quaid> jmbuser: like I said, trying to think of, "If John only has 10 minutes for Fedora Docs today/this week/etc., what is a way he can have a bigger impact than e.g. editing a paragraph."
09:40 < jmbuser> quaid: Things are finally getting under control at work
09:40 < quaid> that's good
09:41 * quaid is going more out of control :)
09:41 < jmbuser> quaid: I would have to say that defining tasks and promoting greater participation...
09:41 < quaid> jmbuser: just a 'leadership thinking' idea I'm passing along, that's all; I often find myself doing something small and silly just to be doing something, and I try to remember to think of an overarching way I can make a difference.
09:42 < jmbuser> quaid: would be a good use of my time right now
09:42 < quaid> for example, if I didn't read that post but instead wrote up our minutes ...
09:42 < quaid> jmbuser: sounds great; let's find a way to make that chatter on the list, too
09:42 < quaid> ok, that's all of that for me
09:42 < quaid> anything else from anyone else?
09:43 < quaid> ok, closing the meeting in 30 seconds ...
09:44 -!- nman64 [n=n-man@fedora/nman64] has joined #fedora-docs
09:44 < jmbuser> +1
09:49 < quaid> </meeting>
16 years, 9 months
FDSCo Meeting 2007-07-17 Summary
by Karsten Wade
Remove this line, then fill in date above along with other details below
Attendees:
-----------
John Babich (jmbuser)
Karsten Wade (quaid)
Ville-Pekke Vainio (vpv)
Summary:
---------
* Reviewed the proposed documentation workflow; pushing final discussion
and ratification to the list.
* Man/info page project progressing with a few hitches, mainly due to
complexity of the problem:
http://vpv.kapsi.fi/blog/2007/07/16/weekly-report-week-28/
* Need to start planning FDSCo election on list
* User Guide -- John is going to focus his time on enabling others to
help, attracting attention to the FUG, and making lots of noise for
every edit or change he does.
16 years, 9 months
help define our workflow, other notes
by Karsten Wade
I captured the below questions and answers during a chat with Jon
Steffan (daMaestro) today. Jon is building our next generation
publishing system. It will make it very easy for _all_ of us to write,
edit, translate, and publish using our favorite tools. It will be 1000x
better than our current publication method on docs.fedoraproject.org.
To open, I'll answer Jon's questions and my answers to him, then give
the rest of everything so you can put in your answers and thoughts and
questions.
== Jon's Questions ==
Jon is working on some diagrams, and his pretty pictures depend on our
answers.
1) assuming we *can* do full staging (ie .. what has been
rendered stays live until another render is issued); what is
the default state for the edit? draft?
## KW - I think a default of 'draft' makes sense; that way we
don't lock the document for editing until we really mean it.
2) at the published state... do we *force* a stage (eg.. you
can't edit the published.. (well.. you *can* but you really
just edit a clone that is a staged version)
## Clarification -- staging in this case means, changes to a
document are not shown live until the workflow on the new staged
version is complete
## KW - Yes, I think so. As long as an admin can force an
update to content via some reasonable method for the rare
occasions (defacing, security risk, data risk, etc.), I think it
is reasonable to keep a document published until it has passed
through a QA and translation stage.
3) at draft, i assume all members can edit
## KW - Yes. We want all members of Fedora Docs to be able to
edit in this workflow.
4) at stable, i assume only key members can edit... and this
is where we go to translations
## KW - This makes sense. Translators find mistakes or have
questions/clarifications for the original; an editor or original
owner needs to be able to fix those and push the content back
for translation (generate a new POT, alert translators with open
PO files, whatever.) How much of this can be done through
Plone? Through CVS?
5) "rendering" ... aka making all languages available (that
we have translations for at least) is staged and the
external rendering engine (some simple python xmlrpc daemon
that handles heavy lifting and security sensitive stuff) is
what actually does the push into the zodb (plone content)
for the live version
we can render whenever we want
## KW - We cooked up this idea the other day on IRC, talking
with other Infrastructure folks. This lets us off-load riskier
and more intensive operations to back-end services. Front-end
Plone doesn't have to deal with committing to CVS or rendering
XML to HTML and PDF.
6) does *every* edit go back into CVS.. or do we want to
have inner plone staging with another state that is "commit"
... so we have to exclusively commit back to CVS
## KW - once a document is in our custom workflow, it should
have all edits go to CVS. For example, a writer or
editor/reviewer needs to be able to open the document as a
direct file in their $editor. All edits have to be synced to
the same control management, once it is in formal document
space.
Not formal doc space == Wiki, personal Plone space,
fedorapeople.org
Formal doc space == XML builds into HTML hosted via a CMS
(Plone)
== More Notes ==
Staging == the ability to edit a new version of a document while the old
version stays "live" and viewable to the public.
Free drafting happens in the personal Plone space -- default
workflow[2], no constraints, show others, peer review, etc.
When a writer is first ready for a review/editor, they use the default
workflow[2] to put it in an editor's queue for review. The editor(s)
and writer(s) can use this to go back and forth until they are satisfied
they have a document ready for publication.
The default workflow state of 'published' is a good starting point for a
document that is ready to go into CVS and the formal Fedora Docs
workflow[1]. Content could also come in from other sources, such as the
Wiki (through CVS), from CVS, or from a Plone document.
Once in the workflow, a document moves from draft to stable. Stable is
where translations occur. Anywhere along the way, a document can be
rendered and committed to CVS.
Staging works here by letting us keep a live version from updating
without it first being translated. This keeps documents from being out
of sync.
Remember, this is all for our formal, published documents. This is
where content goes after we do lots of collaboration on writing it via
our favorite $editor program, which could be Plone or it could be vi or
it could be the Wiki. Docs/Beats => release notes is the model we are
following.
[1]
== Fedora Docs Custom Workflow ==
'draft' - new content
'commit' - committed to CVS
'stable' - ready for translation
'render' - offload rendering of XML in all $lang
'published' - grab render and publish
More details coming, based on answers to our questions.
[2]
== Default Workflow ==
Default roles:
owner - owns the document (wrote it)
reviewer - reviews and edits the document
manager - full permissions to the documents of the people they manage
The default workflow looks like this:
'private' (only owner can edit and see) [and managers]
'public draft' (everyone can see, owner can edit) [managers can always
do whatever]
'submitted' (reviewers can edit, owner can not, everyone can view)
'published' (everyone can see)
'revoked' [from submitted] gives edit rights back to owner
'rejected' [from submitted] moves back so owner can edit, with a
notice of rejection and why
... and a few other things
most of that will be customized to some degree
--
Karsten Wade, 108 Editor ^ Fedora Documentation Project
Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject
quaid.108.redhat.com | gpg key: AD0E0C41
////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
16 years, 9 months
Self Introduction - Where Do I Start?
by Mustafa Qasim
Hello to all folks there ...well Mustafa here from Pakistan. I am doing my
Bachelor's in software engineering right now. I started using Linux a year
ago when I did a system and network administration course on RHL 9. After
that I didn't got any chance to do something more with Linux. After that I
get familiarized with the Open Source theory and truly I loved it, so that's
y I chose JAVA for jumping into professional programming career INSTEAD of
'.NET' bcoz i want to move on further with Linux.
I m using FC 6 right now n when I came here I loved to c u all doing great
work here. I would also like to be a part of FC community but didn't know
where to start. I would love to work on Fedora documentation OR
internationalization project for URDU language support in Fedora but as
being a newbie at town I didn't know that how much knowledge is required to
get on work in a particular project.
I will love to hear whatever you have to share for me. I will be more then
happy to get advice or comments or suggestions from u folks there. :)
--
Mustafa Qasim
Lahore, Pakistan
Cell: 0321-6614972
URL: http://www.mustu.info
16 years, 9 months
samba+ldap tutorial on fedora7
by Deependra Singh Shekhawat
Hi,
As I mentioned few days ago here
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=129739
I have managed to come up with a edited version of the samba+ldap
tutorial. That is working at the moment.
I have re-written the doc according to the newer version of Fedora (that
is Fedora 7) and have to edit alot of things. Other missing areas in the
earlier tutorial are also filled in. Most importantly the parts on how
to configure a Windows client and using yum to install and update the
required software. Also this guide covers on howto get a master DNS
server up and running because DNS must be working for this thing to
work.
So far I have managed to configure Windows 2000 Professional client (and
it's working great) as I don't have Windows XP machine at the moment but
will soon be doing that.
I want to have cvs access so that I can start uploading the source xml.
If someone like to see the edited version I have it at the moment in
openoffice.org format at
http://freeshells.ch/~source/smbldap-f7-howto.odt
Will soon be going to port it into Docbook and according to the
fedoraproject Docs Writing guidelines.
Thanks
Deependra Singh Shekhawat
16 years, 9 months
