The FreeBSD Diary

The FreeBSD Diary (TM) Remember
I remember
[ HOME | TOPICS | INDEX | WEB RESOURCES | BOOKS | CONTRIBUTE | SEARCH | FEEDBACK | FAQ | FORUMS ]

Article Feedback - There is room to improve
 New Topic  |  Go to Top  |  Go to Topic  |  Search  |  Log In   Newer Topic  |  Older Topic 
 Yes, contribute, but how?
Author: Michael Galassi 
Date:   08-04-02 23:41

I suspect there are many of us out there who have the knowledge and the desire to help but have had no success submitting code, documents, HOWTOs, etc. For example, the one answer to the FAQ that you mention in your article, what do I do with it once written? Let us say that I have a mini-HOWTO written on setting up jails under FreeBSD-STABLE, then what? How about if I've written a set of scripts to make mounting ISO images on vn devices more intuitive? I've a friend at work who has made several bug fixes to the Gimp and submitted them, they got ignored more than once. He now just patches his local copy and calls it good enough. Can't say I blame him.

-michael

Reply To This Message
 
 Re: Yes, contribute, but how?
Author: bobb 
Date:   09-04-02 00:23

There is an article on the web site that covers this
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/index.html

For your HowTo's above you would send a pr (problem report)
under the "doc" Category either from the web site http://www.freebsd.org/send-pr.html
or through the command send-pr(1).

Although before that it might be an idea to have a read through
the fdp-primer (FreeBSD Doc Project Primer) http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/.
It may also be an idea to subscribe to the doc mailing list, and perhaps post your article (or a link to it) to -doc or a more
relavant list to get some feedback on it before submitting the PR.

Hope this helps.

- bobb

Reply To This Message
 
 Re: Yes, contribute, but how?
Author: Dan Langille 
Date:   09-04-02 01:45

Michael Galassi wrote:
>
> I've
> a friend at work who has made several bug fixes to the Gimp
> and submitted them, they got ignored more than once. He now
> just patches his local copy and calls it good enough. Can't
> say I blame him.

Submitted them where? Let's assume the freebsd-ports mailing list. If a PR was filed, he should be able to look it up and find out what happened. If the PR is open, you start posting message to the -ports mailing list and CC the maintainer.

It's rather difficult to comment on your friend's situation without knowing the big picture.

Reply To This Message
 
 Re: Yes, contribute, but how?
Author: nova 
Date:   11-04-02 20:20

well
dont wanna be a wuss but i've submited some few bugs/ideas for some few ports and ALWAYS get ignored!
i've only written to the maintainer though

Reply To This Message
 
 Re: Yes, contribute, but how?
Author: Dan Langille 
Date:   12-04-02 04:49

If you get no reply from the maintainer, submit a PR with your patches. And keep on freebsd-ports, mentioning that the maintainer has not replied and get someone to commit the PR.

Reply To This Message
 
 Re: Yes, contribute, but how?
Author: Giorgos Keramidas 
Date:   14-04-02 07:06

Michael Galassi wrote:

> For example, the one answer to the FAQ that you
> mention in your article, what do I do with it once
> written? Let us say that I have a mini-HOWTO written
> on setting up jails under FreeBSD-STABLE, then what?

Then, if you feel that this should be included in the
documentation set of FreeBSD you submit it to the FDP
(FreeBSD Documentation Project). This is documented in
various places at www.FreeBSD.org, like the article on
contributing already mentioned. If all that the article
describes, about bug reports, and using send-pr seems too
much for you, you can even send your documents in plain
ASCII text to freebsd-doc@FreeBSD.org and some doc-hacker
will do what is required to have them added in the collection
of SGML docs.

> How about if I've written a set of scripts to make
> mounting ISO images on vn devices more intuitive?

> I've a friend at work who has made several bug fixes
> to the Gimp and submitted them, they got ignored more
> than once. He now just patches his local copy and
> calls it good enough. Can't say I blame him.

Is the bug FreeBSD specific, or is it something that the
Gimp needs changed on all platforms that it runs on? If
the bug shows up only on FreeBSD, then I'm sure the
maintainer of the Gimp port in FreeBSD will gladly merge
the patch to the port if you let him know. Note however,
that if this is a bug that needs to be patched in Gimp's
source (because it's not a FreeBSD bug, but some problem
that Gimp has in all the platforms it runs on), you will
kindly be asked to send the changes to the maintainers
of Gimp too. This way, FreeBSD's version of Gimp will
be as close as possible to the officially released version
of the program, which is a nice thing ;-)

- Giorgos

Reply To This Message
 Forum List  |  Threaded View   Newer Topic  |  Older Topic 


 Forum List  |  Need a Login? Register Here 
 User Login
 User Name:
 Password:
 Remember my login:
   
 Forgot Your Password?
Enter your email address or user name below and a new password will be sent to the email address associated with your profile.
How to get the most out of the forum

phorum.org