Signing up for Implementation Development Teams

[Brian Behlendorf]

The Concrete Implementation workgroup has been charged with whittling the
proposed implementions of the Abstract Model down to a single, specific
implementation. This is a crucial step on the path to building a
reference software stack and conformance test suite that can be used by
participants during the pilot phase and beyond. The list of proposals is
being tracked at the bottom of the Specifications and Service Descriptions
page:

http://nhindirect.org/specifications+and+service+descriptions

There are three listed there today, corresponding roughly to the proposed
protocols to use for the "HISP-to-HISP" backbone. There is yet time for
more - XMPP has been suggested, for example. The three there have a
fleshed-out proposal behind each of them, describing how they apply to the
abstract model.

Now it is time to advance each proposal forward, so as to determine
which one(s) can meet the "minimum threshold" being established by the
Concrete Implementation WG, with minor tweaks to be expected over the
next few days:

http://nhindirect.org/Concrete+Implementation%3B+Minimum+Threshold+for+Recommendation

To do this, we need Implementation Group members to get involved in one or
more proposals forward. Those who are not IG members are more than
get involved in this way as well. To volunteer, please visit the
"Development Team" pages corresponding to the proposal you wish to get
involved with, e.g.:

http://nhindirect.org/SMTP+Implementation+Development+Team
http://nhindirect.org/REST+Implementation+Development+Team
http://nhindirect.org/IHE+Implementation+Development+Team

and leave your name and affiliation on the page in some logical way. We
will need participants who have had experience with software development,
and can help us actually get to "running code" quickly, so feel free to
bring in a more technical participant in your place.

The SMTP page is the most fleshed-out so far, if you'd like a template.
We will be looking for organizers for each team, volunteers who can go the
extra mile to help rally the efforts forward. Feel free to self-select.
We also ask each development team to use the Wiki page for the team (and
comments thereupon) as your central communications hub, so that new
participants can be self-sufficient.

By the May 6th in-person meeting, we would like each proposal to be on its
way towards the minimum threshold goals, so as to allow us to have a
"gut-check" conversation about whether we are ready to nail it down then,
or that we would benefit from continuing the parallel process a little
while longer.

Thank you,

Brian

--
You received this message because you are subscribed to the Google Groups "nhindirect-discuss" group.
To post to this group, send email to nhindirec...@googlegroups.com.
To unsubscribe from this group, send email to nhindirect-disc...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/nhindirect-discuss?hl=en.

[Brian Ahier]

This is such an ambitious and worthy project! I am forwarding this to
some folks that have thus far not been able to participate much, but
hopefully would have the time to work on one of the more narrowly
focused Implementation Development teams.
Nice work pulling this together Brian :-)

On Apr 27, 10:14 pm, Brian Behlendorf <br...@behlendorf.com> wrote:
> The Concrete Implementation workgroup has been charged with whittling the
> proposed implementions of the Abstract Model down to a single, specific
> implementation.  This is a crucial step on the path to building a
> reference software stack and conformance test suite that can be used by
> participants during the pilot phase and beyond. The list of proposals is
> being tracked at the bottom of the Specifications and Service Descriptions
> page:
>
> http://nhindirect.org/specifications+and+service+descriptions
>
> There are three listed there today, corresponding roughly to the proposed
> protocols to use for the "HISP-to-HISP" backbone.  There is yet time for
> more - XMPP has been suggested, for example.  The three there have a
> fleshed-out proposal behind each of them, describing how they apply to the
> abstract model.
>
> Now it is time to advance each proposal forward, so as to determine
> which one(s) can meet the "minimum threshold" being established by the
> Concrete Implementation WG, with minor tweaks to be expected over the
> next few days:
>

> http://nhindirect.org/Concrete+Implementation%3B+Minimum+Threshold+fo...

>
> To do this, we need Implementation Group members to get involved in one or
> more proposals forward.  Those who are not IG members are more than
> get involved in this way as well.  To volunteer, please visit the
> "Development Team" pages corresponding to the proposal you wish to get
> involved with, e.g.:
>

> http://nhindirect.org/SMTP+Implementation+Development+Teamhttp://nhindirect.org/REST+Implementation+Development+Teamhttp://nhindirect.org/IHE+Implementation+Development+Team

[Brett Peterson]

I've put some initial content in the REST Implementation page.
Everything in it is up for debate, but it's a starting point. If
you'd like to join this effort, please come sign up here!

http://nhindirect.org/REST+Implementation+Development+Team

Brett