[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freebsd-hackers
Subject:    Re: Need Help regarding contribution to Free BSD Projects
From:       rahul gupta <rkg10100 () gmail ! com>
Date:       2017-08-12 6:15:41
Message-ID: CANvmR=bfg9p61GpjsHcRiQ8X-iaNK_bo6zsVKyRjN_ubSKqzQQ () mail ! gmail ! com
[Download RAW message or body]

This is great, thank you so much!

On 11-Aug-2017 1:24 AM, "Rick Macklem" <rmacklem@uoguelph.ca> wrote:

> rahul gupta wrote:
> [good stuff snipped]
> >>> Hi Team,
> >>> Actually I am looking for Some Dev and i keen to work on File system so
> >>> please any body assigned me some work related to file system and guide
> me
> >>> the way that how can start contributing because i am quite beginner to
> this
> >>> so please help me .
> >>>
> Well, first off I'll make a few "big picture" comments...
> - If you were expecting to hear from someone with a "go work on this", it
> won't
>   happen.
>   Why?
>   Well, there isn't anyone. The FreeBSD project doesn't have a CTO or a
> committee
>   of wizards that make technical decisions. It is much more an "anonymous
> collective".
>   - Basically, you find something that interests you. At some point, when
> you have a
>     patch that you think the project will find useful, you propose it
> (either on one
>     of the email lists or reviews.freebsd.org). If others think it is
> useful, hopefully
>     some committer will pick it up and do the commit.
>    - After a while, the committers get tired of doing this and suggest you
> become a
>      committer and do the commits yourself, etc...
> There is a group called "core" which are elected by the committers, but
> they mostly
> deal with logistics and not technical issues. They are the ones that
> decide if an
> individual is to become a committer.
>
> Now, since you mentioned "file systems", I will note that Fuse is in need
> of some TLC.
> (There is a kernel component, which a few of us know a little about and a
> library
>  that at least I, know nothing about. It also could use a bunch of testing
> with different
>  file systems.)
> Here's a recent email thread related to Fuse:
> http://docs.FreeBSD.org/cgi/mid.cgi?87y3r0ankb.fsf
>
> In general, you'll want to join several email lists and what gets
> discussed on them
> will give you an idea of what people are working on. (If you become a
> committer,
> you pretty well have to watch these lists, so you might as well start
> now;-)
> A few I'm on are: freebsd-fs@, freebsd-current@, freebsd-stable@,
> freebsd-arch@
>
> You will need a system that you can test source changes against head on,
> so you should
> set up a head/current system. (head/current refers to the src tree found at
> repo.freebsd.org/base/head and is where the stable and release branches
> are
> created from, so that's where source patches go first). I think you can get
> read-only anonymous access to the subversion repo, but I haven't done so.
>
> Good luck and have fun with it, rick
_______________________________________________
freebsd-hackers@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
[prev in list] [next in list] [prev in thread] [next in thread]