Send Netdot-devel mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Netdot-devel digest..."
Today's Topics:
1. Re: commit access and future of netdot? (Carlos Vicente)
----------------------------------------------------------------------
Message: 1
Date: Wed, 17 Feb 2016 14:05:43 -0500
From: Carlos Vicente <[email protected]>
Subject: Re: [Netdot-devel] commit access and future of netdot?
To: Matt Zagrabelny <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252
Hi Matt,
Sorry for the long delay.
I?m very glad to hear that you find Netdot useful and that you intend to
contribute.
The project continues to develop, and I?m still the main point of contact. Many
people contribute patches. At the moment Anton Berezin is working on
significant improvements regarding locations, which in turn will allow us to
document rack information for assets. More on that soon.
For bug reports and feature requests, a Redmine ticket is probably the best
option. If you want to discuss feature ideas or plans more interactively, then
this mailing list (or even the users mailing list) might be more useful.
When you are ready to contribute code, Github pull requests are the way to go.
Best,
cv
On Feb 4, 2016, at 1:23 PM, Matt Zagrabelny <[email protected]> wrote:
> Hey Carlos and other devs,
>
> Thanks for Netdot. It is a great piece of software and I'm excited to
> begin using it and hopefully contributing patches and pull requests.
>
> That said, what do you folks see for the future of the project?
>
> How many people are working on features, bugs, etc.?
>
> How many users have commit access?
>
> Is this mailing list the best way to communicate that one plans on
> working on a feature, so another group doesn't work on the same
> feature simultaneously?
>
> Thanks for adding to the dialogue.
>
> Cheers!
>
> -m
> _______________________________________________
> Netdot-devel mailing list
> [email protected]
> https://osl.uoregon.edu/mailman/listinfo/netdot-devel
------------------------------
_______________________________________________
Netdot-devel mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
End of Netdot-devel Digest, Vol 107, Issue 5
********************************************
