.Net developers collaboration

Hi folks,

A small group of .Net developers on campus have been talking recently
about collaborating on common code, frameworks and repositories and
we thought we should expand to include other campus .Net programmers
in thinking about reusable/shared code so we could share best
practices and spare everyone potentially redundant effort.

To facilitate the discussion we've create a listserv for .Net
developers (dotnetnet-list_at_lists.berkeley.edu) which you can
subscribe to using Majordomo (email Majordomo_at_lists.berkeley.edu with
subscribe dotnetnet-list in the body of the message).

We are also going to hold a meeting so that interested parties can
participate actively in investigating and developing resources we can
all share. This will be a 'hands on' meeting and we expect to form
work groups that will work together to discover common needs and best
practices and report back to the group!

Who: Anyone interested in developing .Net applications!

When: February 28 from 12-1:30 (feel free to bring lunch -- we'll
provide some treats for the group)

Where: TBD - we'll find a room after we get a head count so please
RSVP
(https://students.berkeley.edu/osl/rsvp/rsvp.asp?todo=details&EventId=1082575321)
ASAP!

What: Meeting to discuss .Net development efforts with the goal of
creating teams to conduct analysis of various aspects and report back
and then divide up work efforts and collaborate on development of
common tools/architecture.

We're going to propose a number of topics for work groups to tackle
and get to work (see below). The goal is for each group to produce
deliverables for the multitude of issues that affect us all.

Want to attend? Please RSVP!
https://students.berkeley.edu/osl/rsvp/rsvp.asp?todo=details&EventId=1082575321

Proposed Working Groups:

Common Code Libraries/Web Services Group
Description: This team will survey .Net developers about needs and
resources available for common methods and will make recommendations
about which should be code libraries and which should (also) be Web
Services. It is expected that this group will survey the UCB .Net
developer community, create a list of generic core code libraries
required by developers, propose candidates for libraries that should
be Web Services, indicate which exist as .Net libraries, and which
exist as Web Services and present the list of candidates to the group
within three weeks. The details of the libraries are not the
responsibility of this group in this phase - the team can provide
examples of requirements to the group, but full elaboration of the
libraries will be completed in a subsequent phase. This group will
also survey .Net developers about data naming conventions (e.g. PESC,
UBL, BABL) that should be adopted as the basis for data exchange.
Timeframe: 1 month
Time Commitment: 10-20 hours

Coding Framework Group
Description: Evaluate coding styles and techniques to develop
recommendations for a coding framework. Explore the use of existing
frameworks such as Spring.Net, DotNet Nuke, etc. Evaluate unit
testing techniques and evaluate testing frameworks.
Timeframe: 1-2 months
Time Commitment: 10-20 hours

Code Sharing Group
Description: Evaluate options for sharing code between .Net
developers and across campus. Discuss repository options for both the
short-term and long-term. Explore the use of Subversion, Source Safe,
Team Server, Web Farm, etc.
Timeframe: 2 weeks
Time Commitment: ~5 hours

UI/"skinning"/"Themes"/.Net Controls Group
Description: Explore approaches to using stylesheets, XML/XSL,
masterpages and themes for "skinning" applications; investigate
sharing common validation routines and error handling methods; look
into usage of XSLT transformations for printing, distributing content, etc.
Timeframe: 2-4 weeks
Time Commitment: 10-15 hours

Security/Identity Management/Authorization Group
Description: This team will explore best practices for secure and
authenticated transmission of data via Web Services, and the
possibility of creating a basic shared role-based authorization service.
Timeframe: 4-6 weeks
Time Commitment: 10-20 hours

Regards,

The Student Affairs .Net Team
(Michael Beeson, Tim Heidinger, Tom O'Brien, Cathy Taruskin)

------------------------------------------------------------------------
The following was automatically added to this message by the list server:

For information about Micronet, including subscribing to
or unsubscribing from its mailing list and finding out
about upcoming meetings, please visit the Micronet Web site:
<http://micronet.berkeley.edu/>.
Received on Tue Feb 20 2007 - 14:55:48 PST