[
https://issues.apache.org/jira/browse/NET-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576281#action_12576281
]
James Carman commented on NET-187:
----------------------------------
Niall,
While I agree with the general do-ocracy idea (and the folks who have worked on
Net have done a great job), I don't necessarily agree that projects should be
allowed to just change their scope whenever they choose. Part of the proposal
to join Apache Commons is the scope of the project. Projects are allowed in
after a vote by the PMC based on the proposal. There should be some assurance
that the project is going to stick to that proposed scope. What happens if a
project decides to change its scope and that new scope would have made it fail
to enter Commons in the first place because it violates the charter?
Now, I'm not saying that's what's going on here with Net at all. I wouldn't
really have a problem with Net changing its scope to include server
implementations, but it hasn't been officially proposed.
Another point to consider is that once you start adding in trivial server
implementations for some protocols, then it stands to reason that folks might
expect that for some of the other protocols also. Now, we don't always have to
do what we're asked, but we should try to have some consistency and having one
server implementation for one specific protocol and none of the others isn't
really consistent (IMHO).
> TFTP Server for commons net
> ----------------------------
>
> Key: NET-187
> URL: https://issues.apache.org/jira/browse/NET-187
> Project: Commons Net
> Issue Type: New Feature
> Affects Versions: 1.4
> Reporter: Dan Armbrust
> Priority: Minor
> Fix For: 2.0
>
> Attachments: TFTPServer and Tests.patch
>
>
> Bug for attaching TFTP Server.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
