Form 3 (in 2016WP/ROBUST-10_MARTIN)

Saved Values

in subcontext 'abstract'

description: 'Context ------- Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE) consisting of: - a website (nemo-ocean.eu) which serves as a public portal - a Forge (forge.ipsl.jussieu.fr/nemo) composed of a SVN repository and a web project management software Trac - 3 mailing lists '[Nemo]', '[nemo_ticket]' & '[Nemo_st]' respectively for the users, the external notification system and the developers community In anticipation of the end of life of the server hosting the website (planned for Q1 2017), I propose a global evolution which will impact all the components but will also remove most of the existing flaws and fill several lacks: - Decentralize the IT system to improve its availability and security - Reduce the duplication and the scattering of the content, and facilitate its edition - Limit the needs for any support or specific development, and simplify the administration tasks To be honest, this will give a little more work day by day to the NEMO Officers which must be balanced with more autonomy. If all goes according to the plan, this evolution will be almost harmless for the users and will make life easier for the developers. New components scheme --------------------- The main strategy is to reach a compromise between the different groups with distinct needs and our integrated tools. A predetermined rule of one tool per group brings to the next scheme: - Public -> Current website reduced to its public content (~ static) * No more registration for Forge access (SVN + Trac), nor private content for other groups (i.e 'Users, Developers or ST) * Visitors can always submit publications or associated projects with later validation and contact ST * Apart administrators, only 1 editor per institute (NEMO Officer) - Users -> New Forge for Users (SVN "slave" repository + Trac-like web application) in the hosted service 'SourceSup' by RENATER (https://sourcesup.renater.fr) * Standalone authentication system (copy of user database is considered, except for pre-registered users from french research network) * Own bug tracking system (completely isolated from existing Trac system) * New complete wiki (a shared work must be carried on this particular topic) - Developers/Contributors -> Existing SVN repository as a "master" repository with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> Current Trac application will become the only management portal by upgrading its features. Particular case of the mailing lists ------------------------------------ Together a transfer of the present mailing lists from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (https://groupes.renater.fr/sympa). It is an opportunity to redefine their object and/or change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address 'news@nemo-ocean.eu', identified later by '[News]' -> No prefix, open access but no posting allowed except from owners i.e. ST via NEMO Officers. - '[nemo_ticket]' will remain a notification list with a custom address 'forge@nemo-ocean.eu', identified later by '[Forge]' -> Prefix will depend on the triggering action ('[Commit]'|'[Forum]'|'[Ticket]'), open access but no posting allowed except notifications from either the IPSL Forge or the new Users Forge. - '[Nemo_st]' will become a confidential list with a hidden address 'systeam@nemo-ocean.eu', identified later by '[Systeam]', and will be reserved now for internal significant subjects (no more notifications or support) -> No prefix, subscription controlled by NEMO Officers, no external posting. - '[Contact]': a new mailing list 'contact@nemo-ocean.eu' will be created regarding all communication activities of the different forms from the new website (message, publication or project submission). It will include the administrators (me, Claire & Mathieu) and the editors (NEMO Officers). Critical point -------------- Since In the future, it would mean that anyone who wants to get in touch with us for support will have to open a forum discussion or a ticket in the new Forge. It will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation. ' by nicolasmartin2016-06-30T21:18:04+02:00
implementation: 'This evolution must happen by steps, from the simplest and the easiest actions to the most critical part (switch . At this stage, I emphasize on the shared work that will have to be done on the Users Forge. From the content of the users area in the website, we need probably to redefine and reconsider it for the making of the new wiki for users. The schedule is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Independent operations on components with no external interference (few weeks) - Website * New collaborative ST work gradually move to IPSL Trac (agenda, reports, document design & sharing, wikis, ...) * - IPSL Forge: NEMO officers appointed as project administrators for the NEMO project (and for convenience NEMO officers appointed as Trac permissions administrator - NEMO Forge * Install several plugins to enhance the Trac application (agenda, discussion forum, form , custom notification, private wiki, ...) * Develop an cron script to: # Check for a new IPSL developer account linked to NEMO, configure it and and inform '[Systeam]' owners for subscription # Synchronize all Trac profiles from their respective IPSL Forge account (name, email & office) # Update the local mailing list of developers for further notifications * Replace the global notification to '[Nemo_st]' (commit, forum, ticket & wiki) by a new customizable system (hook or plugins) # Commit (hook) : output diff replace by changeset link, sender 'SVN Notification <nemo@forge.ipsl.jussieu.fr>' & prefix '[Commit]' with the extra info of the commit path # Forum (built-in system) : sender 'Trac Notification <nemo@forge.ipsl.jussieu.fr>' & prefix '[Forum]' # Ticket (plugin attached to workflow action): creation, resolution or reopening notified to all developers, others modifications notified only to reported people and '[Forge]'. Sender 'Trac Notification <nemo@forge.ipsl.jussieu.fr>' & prefix '(Re: )?[Ticket]' for thread grouping # Wiki (plugin works by subscription) : sender 'Trac Notification <nemo@forge.ipsl.jussieu.fr>' & prefix '[Wiki]' - Mailing lists * "" '[Contact]', [Forge], '[News]' & '[Systeam]' on 'Universalistes' service * Create a CRU ("Compte Réseau Universel") account for each NEMO Officer and appoint them as owners for '[News]' & '[Systeam]', add them to '[Contact]' * Switch from '[nemo_ticket]' to '[Forge]' for low risk beta testing 2) Establishment of the Users Forge (2 to 3 months) - Website: enable for a new user the subscription to '[News]' in addition of '[Nemo]' - Users Forge (offline or hidden) * Initialise the new repository and the replication from IPSL repository, then monitor the synchronization * Configure the new SCM (bug tracking system, forum, wiki, ...) * Transfer and update user content from the website: user guides, reference configurations pages, FAQ & utilities * Investigate the possibility of versionning the new wiki pages with the code repository - Mailing lists * Copy the missing members of '[News]' from '[Nemo]' * Begin to use '[News]' & '[Systeam]' and keep '[Nemo]' & '[Nemo_st]' for external requests. 3) Critical switch of NEMO Users to the new architecture (1~2 whole days for operation) - Website (offline during the process) * Block registration of a new user and turn off the synchronization of the accounts to IPSL Forge. * Private areas will be only accessible to ST for reading. * User connection will not open access to more content i.e public site. * Edit accordingly the public pages regarding the new architecture. - IPSL Forge (online): turn off the remote access from the website accounts - IPSL Trac: review default permissions for basic user (merge 'developer' & 'authenticated' role) - Users Forge (online after website maintenance): * Recover the up-to-date accounts database from website * Open access to previous members from website with the same ID (login/passwd) - Mailing lists: close '[Nemo]' & '[Nemo_st]' so de facto '[News]' & '[Systeam]' will become the ones to use. ' by nicolasmartin2016-06-30T21:18:04+02:00
reviewers: 'Claire Lévy' by nicolasmartin2016-03-08T20:44:48+01:00
manual: 'NR' by nicolasmartin2016-03-08T17:12:34+01:00
action: 'ROBUSTNESS-10 Evolution of the Collaborative Development Environment' by nicolasmartin2016-02-24T18:21:41+01:00
previewers: 'NEMO Officers (Clément Bricaud, Emanuela Clementi, Andrew Coward, Simona Flavoni, Dorotea Iovino & Tim Graham)' by nicolasmartin2016-03-04T15:27:34+01:00
pi: 'Nicolas MARTIN & Mathieu Peltier' by nicolasmartin2016-06-02T17:07:25+02:00

Change History

Changed on 2016-06-30T21:18:04+02:00 by nicolasmartin:

  • implementation changed from
    This evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last. At this stage, I emphasize on the shared work that will have to be done on the Users Forge. From the content of the users area in the website, we need probably to redefine and reconsider it for the making of the new wiki for users. The schedule is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Independent operations on components with no external interference (few weeks) - Website * New collaborative ST work gradually move to IPSL Trac (agenda, reports, document design & sharing, wikis, ...) * - IPSL Forge: NEMO officers appointed as project administrators for the NEMO project (and for convenience NEMO officers appointed as Trac permissions administrator - NEMO Forge * Install several plugins to enhance the Trac application (agenda, discussion forum, form , custom notification, private wiki, ...) * Develop an cron script to: # Check for a new IPSL developer account linked to NEMO, configure it and and inform '[Systeam]' owners for subscription # Synchronize all Trac profiles from their respective IPSL Forge account (name, email & office) # Update the local mailing list of developers for further notifications * Replace the global notification to '[Nemo_st]' (commit, forum, ticket & wiki) by a new customizable system (hook or plugins) # Commit (hook) : output diff replace by changeset link, sender 'SVN Notification <nemo@forge.ipsl.jussieu.fr>' & prefix '[Commit]' with the extra info of the commit path # Forum (built-in system) : sender 'Trac Notification <nemo@forge.ipsl.jussieu.fr>' & prefix '[Forum]' # Ticket (plugin attached to workflow action): creation, resolution or reopening notified to all developers, others modifications notified only to reported people and '[Forge]'. Sender 'Trac Notification <nemo@forge.ipsl.jussieu.fr>' & prefix '(Re: )?[Ticket]' for thread grouping # Wiki (plugin works by subscription) : sender 'Trac Notification <nemo@forge.ipsl.jussieu.fr>' & prefix '[Wiki]' - Mailing lists * "" '[Contact]', [Forge], '[News]' & '[Systeam]' on 'Universalistes' service * Create a CRU ("Compte Réseau Universel") account for each NEMO Officer and appoint them as owners for '[News]' & '[Systeam]', add them to '[Contact]' * Switch from '[nemo_ticket]' to '[Forge]' for low risk beta testing 2) Establishment of the Users Forge (2 to 3 months) - Website: enable for a new user the subscription to '[News]' in addition of '[Nemo]' - Users Forge (offline or hidden) * Initialise the new repository and the replication from IPSL repository, then monitor the synchronization * Configure the new SCM (bug tracking system, forum, wiki, ...) * Transfer and update user content from the website: user guides, reference configurations pages, FAQ & utilities * Investigate the possibility of versionning the new wiki pages with the code repository - Mailing lists * Copy the missing members of '[News]' from '[Nemo]' * Begin to use '[News]' & '[Systeam]' and keep '[Nemo]' & '[Nemo_st]' for external requests. 3) Critical switch of NEMO Users to the new architecture (1~2 whole days for operation) - Website (offline during the process) * Block registration of a new user and turn off the synchronization of the accounts to IPSL Forge. * Private areas will be only accessible to ST for reading. * User connection will not open access to more content i.e public site. * Edit accordingly the public pages regarding the new architecture. - IPSL Forge (online): turn off the remote access from the website accounts - IPSL Trac: review default permissions for basic user (merge 'developer' & 'authenticated' role) - Users Forge (online after website maintenance): * Recover the up-to-date accounts database from website * Open access to previous members from website with the same ID (login/passwd) - Mailing lists: close '[Nemo]' & '[Nemo_st]' so de facto '[News]' & '[Systeam]' will become the ones to use.
    to
    This evolution must happen by steps, from the simplest and the easiest actions to the most critical part (switch . At this stage, I emphasize on the shared work that will have to be done on the Users Forge. From the content of the users area in the website, we need probably to redefine and reconsider it for the making of the new wiki for users. The schedule is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Independent operations on components with no external interference (few weeks) - Website * New collaborative ST work gradually move to IPSL Trac (agenda, reports, document design & sharing, wikis, ...) * - IPSL Forge: NEMO officers appointed as project administrators for the NEMO project (and for convenience NEMO officers appointed as Trac permissions administrator - NEMO Forge * Install several plugins to enhance the Trac application (agenda, discussion forum, form , custom notification, private wiki, ...) * Develop an cron script to: # Check for a new IPSL developer account linked to NEMO, configure it and and inform '[Systeam]' owners for subscription # Synchronize all Trac profiles from their respective IPSL Forge account (name, email & office) # Update the local mailing list of developers for further notifications * Replace the global notification to '[Nemo_st]' (commit, forum, ticket & wiki) by a new customizable system (hook or plugins) # Commit (hook) : output diff replace by changeset link, sender 'SVN Notification <nemo@forge.ipsl.jussieu.fr>' & prefix '[Commit]' with the extra info of the commit path # Forum (built-in system) : sender 'Trac Notification <nemo@forge.ipsl.jussieu.fr>' & prefix '[Forum]' # Ticket (plugin attached to workflow action): creation, resolution or reopening notified to all developers, others modifications notified only to reported people and '[Forge]'. Sender 'Trac Notification <nemo@forge.ipsl.jussieu.fr>' & prefix '(Re: )?[Ticket]' for thread grouping # Wiki (plugin works by subscription) : sender 'Trac Notification <nemo@forge.ipsl.jussieu.fr>' & prefix '[Wiki]' - Mailing lists * "" '[Contact]', [Forge], '[News]' & '[Systeam]' on 'Universalistes' service * Create a CRU ("Compte Réseau Universel") account for each NEMO Officer and appoint them as owners for '[News]' & '[Systeam]', add them to '[Contact]' * Switch from '[nemo_ticket]' to '[Forge]' for low risk beta testing 2) Establishment of the Users Forge (2 to 3 months) - Website: enable for a new user the subscription to '[News]' in addition of '[Nemo]' - Users Forge (offline or hidden) * Initialise the new repository and the replication from IPSL repository, then monitor the synchronization * Configure the new SCM (bug tracking system, forum, wiki, ...) * Transfer and update user content from the website: user guides, reference configurations pages, FAQ & utilities * Investigate the possibility of versionning the new wiki pages with the code repository - Mailing lists * Copy the missing members of '[News]' from '[Nemo]' * Begin to use '[News]' & '[Systeam]' and keep '[Nemo]' & '[Nemo_st]' for external requests. 3) Critical switch of NEMO Users to the new architecture (1~2 whole days for operation) - Website (offline during the process) * Block registration of a new user and turn off the synchronization of the accounts to IPSL Forge. * Private areas will be only accessible to ST for reading. * User connection will not open access to more content i.e public site. * Edit accordingly the public pages regarding the new architecture. - IPSL Forge (online): turn off the remote access from the website accounts - IPSL Trac: review default permissions for basic user (merge 'developer' & 'authenticated' role) - Users Forge (online after website maintenance): * Recover the up-to-date accounts database from website * Open access to previous members from website with the same ID (login/passwd) - Mailing lists: close '[Nemo]' & '[Nemo_st]' so de facto '[News]' & '[Systeam]' will become the ones to use.
  • description changed from
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE) consisting of: - a website (nemo-ocean.eu) which serves as a public portal - a Forge (forge.ipsl.jussieu.fr/nemo) composed of a SVN repository and a web project management software Trac - 3 mailing lists '[Nemo]', '[nemo_ticket]' & '[Nemo_st]' respectively for the users, the external notification system and the developers community In anticipation of the end of life of the server hosting the website (planned for Q1 2017), I propose a global evolution which will impact all the components but will also remove most of the existing flaws and fill several lacks: - Decentralize the IT system to improve its availability and security - Reduce the duplication and the scattering of the content, and facilitate its edition - Limit the needs for any support or specific development, and simplify the administration tasks To be honest, this will give a little more work day by day to the NEMO Officers which must be balanced with more autonomy. If all goes according to the plan, this evolution will be almost harmless for the users and will make life easier for the developers. The main strategy is to reach a compromise between the different groups with distinct needs and our integrated tools. A predetermined rule of one tool per group brings to the next scheme: - Public -> Current website reduced to its public content (~ static) * No more registration for Forge access (SVN + Trac), nor private content for other groups (i.e 'Users, Developers or ST) * Visitors can always submit publications or associated projects with later validation and contact the webmasters * Only - Users -> New Forge for Users (SVN "slave" repository + Trac-like web application) in the hosted service 'SourceSup' by RENATER (https://sourcesup.renater.fr) * Standalone authentication system: a copy of the existing user accounts is considered, except for pre-registered users from french research network) * Own bug tracking system * New complete wiki (a shared work must be carried on this particular topic) - Developers/Contributors -> Existing SVN repository as a "master" repository with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> Current Trac application will become the only management portal by upgrading its features. Together a transfer of the present mailing lists from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (https://groupes.renater.fr/sympa). It is an opportunity to redefine their object and/or change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address 'news@nemo-ocean.eu', identified later by '[News]' -> No prefix, open access but no posting allowed except from owners i.e. ST via NEMO Officers. - '[nemo_ticket]' will remain a notification list with a custom address 'forge@nemo-ocean.eu', identified later by '[Forge]' -> Prefix will depend on the triggering action ('[Commit]'|'[Forum]'|'[Ticket]'), Open access but no posting allowed except notifications from either the IPSL Forge or the new Users Forge. - '[Nemo_st]' will become a confidential list with a hidden address 'systeam@nemo-ocean.eu', identified later by '[Systeam]', and will be reserved now for internal significant subjects (no more notifications or support) -> No prefix, subscription controlled by NEMO Officers, no external posting. Also a new mailing list 'contact@nemo-ocean.eu', identified later by '[Contact]', will be created for external request or form submission from the website (no support through this) and will include the administrators and the editors of the website (NEMO Officers). In the future, it would mean that anyone who wants to get in touch with us for support will have to open a forum discussion or a ticket in the new Forge. It will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation.
    to
    Context ------- Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE) consisting of: - a website (nemo-ocean.eu) which serves as a public portal - a Forge (forge.ipsl.jussieu.fr/nemo) composed of a SVN repository and a web project management software Trac - 3 mailing lists '[Nemo]', '[nemo_ticket]' & '[Nemo_st]' respectively for the users, the external notification system and the developers community In anticipation of the end of life of the server hosting the website (planned for Q1 2017), I propose a global evolution which will impact all the components but will also remove most of the existing flaws and fill several lacks: - Decentralize the IT system to improve its availability and security - Reduce the duplication and the scattering of the content, and facilitate its edition - Limit the needs for any support or specific development, and simplify the administration tasks To be honest, this will give a little more work day by day to the NEMO Officers which must be balanced with more autonomy. If all goes according to the plan, this evolution will be almost harmless for the users and will make life easier for the developers. New components scheme --------------------- The main strategy is to reach a compromise between the different groups with distinct needs and our integrated tools. A predetermined rule of one tool per group brings to the next scheme: - Public -> Current website reduced to its public content (~ static) * No more registration for Forge access (SVN + Trac), nor private content for other groups (i.e 'Users, Developers or ST) * Visitors can always submit publications or associated projects with later validation and contact ST * Apart administrators, only 1 editor per institute (NEMO Officer) - Users -> New Forge for Users (SVN "slave" repository + Trac-like web application) in the hosted service 'SourceSup' by RENATER (https://sourcesup.renater.fr) * Standalone authentication system (copy of user database is considered, except for pre-registered users from french research network) * Own bug tracking system (completely isolated from existing Trac system) * New complete wiki (a shared work must be carried on this particular topic) - Developers/Contributors -> Existing SVN repository as a "master" repository with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> Current Trac application will become the only management portal by upgrading its features. Particular case of the mailing lists ------------------------------------ Together a transfer of the present mailing lists from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (https://groupes.renater.fr/sympa). It is an opportunity to redefine their object and/or change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address 'news@nemo-ocean.eu', identified later by '[News]' -> No prefix, open access but no posting allowed except from owners i.e. ST via NEMO Officers. - '[nemo_ticket]' will remain a notification list with a custom address 'forge@nemo-ocean.eu', identified later by '[Forge]' -> Prefix will depend on the triggering action ('[Commit]'|'[Forum]'|'[Ticket]'), open access but no posting allowed except notifications from either the IPSL Forge or the new Users Forge. - '[Nemo_st]' will become a confidential list with a hidden address 'systeam@nemo-ocean.eu', identified later by '[Systeam]', and will be reserved now for internal significant subjects (no more notifications or support) -> No prefix, subscription controlled by NEMO Officers, no external posting. - '[Contact]': a new mailing list 'contact@nemo-ocean.eu' will be created regarding all communication activities of the different forms from the new website (message, publication or project submission). It will include the administrators (me, Claire & Mathieu) and the editors (NEMO Officers). Critical point -------------- Since In the future, it would mean that anyone who wants to get in touch with us for support will have to open a forum discussion or a ticket in the new Forge. It will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation.

Changed on 2016-06-29T22:22:34+02:00 by nicolasmartin:

Changed on 2016-06-29T22:22:34+02:00 by nicolasmartin:

  • implementation changed from
    This evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last. At this stage, I emphasize on the shared work that will have to be done on the Users Forge. From the content of the users area in the website, we need probably to redefine and reconsider it for the making of the new wiki for users. The schedule is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Independent operations on components with no external interference (few weeks) - Website (no particular operation scheduled) * Users still allowed to register and get access to the IPSL Forge (repository and Trac) * New collaborative ST work move to IPSL Trac (agenda, reports, document design & sharing, wikis, ...) - IPSL Trac * NEMO officers appointed as permissions administrator in order to manage their own developers within their institute * Complete by an internal script the Trac profiles from the informations of their IPSL Forge account (name & email) * Replace the global notification for '[Nemo_st]' (wiki and ticket updates) by a customizable system with 2 plugins # Allow the subscription for an email notification of wiki page updates. Sender: 'Trac Wiki Notification <nemo@forge.ipsl.jussieu.fr>', Prefix: '[Wiki]' # Ticket creation & resolution notified to all i.e ST Others modifications notified only to the reporter, the owner and the 'Cc'ers of the ticket Sender: 'Trac Ticket Notification <nemo@forge.ipsl.jussieu.fr>', Prefix: '[Ticket]' - IPSL Forge: NEMO officers appointed as project administrators in order to manage their own developers within their institute - IPSL repository: replace the global notification sending (commits) to '[Nemo_st]' by an internal script which will update the local mailing list every 30 mns from developers group. Sender: 'SVN Commit Notification <nemo@forge.ipsl.jussieu.fr>', Prefix: '[Commit]' - Mailing lists * Create a CRU ("Compte Réseau Universel") account for each NEMO Officer to access the RENATER network * "" '[News]' & '[Systeam]' on 'Universalistes' with Officers as owners 2) Establishment of the Users Forge (2 to 3 months) - Website: enable for a new user the subscription to '[News]' in addition of '[Nemo]' - Users Forge (offline or hidden) * Initialise the new repository and the replication from IPSL repository, then monitor the synchronization * Configure the new SCM (bug tracking system, forum, wiki, ...) * Transfer and update user content from the website: user guides, reference configurations pages, FAQ & utilities * Investigate the possibility of versionning the new wiki pages with the code repository - Mailing lists * Copy the missing members of '[News]' from '[Nemo]' * Begin to use '[News]' & '[Systeam]' and keep '[Nemo]' & '[Nemo_st]' for external requests. 3) Critical switch of NEMO Users to the new architecture (1~2 whole days for operation) - Website (offline during the process) * Block registration of a new user and turn off the synchronization of the accounts to IPSL Forge. * Private areas will be only accessible to ST for reading. * User connection will not open access to more content i.e public site. * Edit accordingly the public pages regarding the new architecture. - IPSL Forge (online): remove access of the website accounts - IPSL Trac: review default permissions for basic user (merge 'developer' & 'authenticated' role) - Users Forge (online after website maintenance): * Recover the up-to-date accounts database from website * Open access to previous members from website with the same ID (login/passwd) - Mailing lists * Close '[Nemo]', '[Nemo_st]' & '[nemo_ticket]'. * De facto '[News]' & '[Systeam]' will become the ones to use. 4) Get ready for the EOL of website server (target Q1 2017) With the previous work done which will reduced the dependency with the other components (less content to manage and no external constraint), We can choose freely between 2 solutions: - simply copy the current website on a new server (easiest) - completely revise the website with a more user-friendly SCM and a pleasant design (needed)
    to
    This evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last. At this stage, I emphasize on the shared work that will have to be done on the Users Forge. From the content of the users area in the website, we need probably to redefine and reconsider it for the making of the new wiki for users. The schedule is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Independent operations on components with no external interference (few weeks) - Website * New collaborative ST work gradually move to IPSL Trac (agenda, reports, document design & sharing, wikis, ...) * - IPSL Forge: NEMO officers appointed as project administrators for the NEMO project (and for convenience NEMO officers appointed as Trac permissions administrator - NEMO Forge * Install several plugins to enhance the Trac application (agenda, discussion forum, form , custom notification, private wiki, ...) * Develop an cron script to: # Check for a new IPSL developer account linked to NEMO, configure it and and inform '[Systeam]' owners for subscription # Synchronize all Trac profiles from their respective IPSL Forge account (name, email & office) # Update the local mailing list of developers for further notifications * Replace the global notification to '[Nemo_st]' (commit, forum, ticket & wiki) by a new customizable system (hook or plugins) # Commit (hook) : output diff replace by changeset link, sender 'SVN Notification <nemo@forge.ipsl.jussieu.fr>' & prefix '[Commit]' with the extra info of the commit path # Forum (built-in system) : sender 'Trac Notification <nemo@forge.ipsl.jussieu.fr>' & prefix '[Forum]' # Ticket (plugin attached to workflow action): creation, resolution or reopening notified to all developers, others modifications notified only to reported people and '[Forge]'. Sender 'Trac Notification <nemo@forge.ipsl.jussieu.fr>' & prefix '(Re: )?[Ticket]' for thread grouping # Wiki (plugin works by subscription) : sender 'Trac Notification <nemo@forge.ipsl.jussieu.fr>' & prefix '[Wiki]' - Mailing lists * "" '[Contact]', [Forge], '[News]' & '[Systeam]' on 'Universalistes' service * Create a CRU ("Compte Réseau Universel") account for each NEMO Officer and appoint them as owners for '[News]' & '[Systeam]', add them to '[Contact]' * Switch from '[nemo_ticket]' to '[Forge]' for low risk beta testing 2) Establishment of the Users Forge (2 to 3 months) - Website: enable for a new user the subscription to '[News]' in addition of '[Nemo]' - Users Forge (offline or hidden) * Initialise the new repository and the replication from IPSL repository, then monitor the synchronization * Configure the new SCM (bug tracking system, forum, wiki, ...) * Transfer and update user content from the website: user guides, reference configurations pages, FAQ & utilities * Investigate the possibility of versionning the new wiki pages with the code repository - Mailing lists * Copy the missing members of '[News]' from '[Nemo]' * Begin to use '[News]' & '[Systeam]' and keep '[Nemo]' & '[Nemo_st]' for external requests. 3) Critical switch of NEMO Users to the new architecture (1~2 whole days for operation) - Website (offline during the process) * Block registration of a new user and turn off the synchronization of the accounts to IPSL Forge. * Private areas will be only accessible to ST for reading. * User connection will not open access to more content i.e public site. * Edit accordingly the public pages regarding the new architecture. - IPSL Forge (online): turn off the remote access from the website accounts - IPSL Trac: review default permissions for basic user (merge 'developer' & 'authenticated' role) - Users Forge (online after website maintenance): * Recover the up-to-date accounts database from website * Open access to previous members from website with the same ID (login/passwd) - Mailing lists: close '[Nemo]' & '[Nemo_st]' so de facto '[News]' & '[Systeam]' will become the ones to use.
  • description changed from
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE) consisting of: - a website (nemo-ocean.eu) which serves as a public portal - a Forge (forge.ipsl.jussieu.fr/nemo) composed of a SVN repository and a web project management software Trac - 3 mailing lists '[Nemo]', '[nemo_ticket]' & '[Nemo_st]' respectively for the users, the external notification system and the developers community In anticipation of the end of life of the server hosting the website (planned for Q1 2017), I propose a global evolution which will impact all the components but will also remove most of the existing flaws and fill several lacks: - Decentralize the IT system to improve its availability and security - Reduce the duplication and the scattering of the content, and facilitate its edition - Limit the needs for any support or specific development, and simplify the administration tasks To be honest, this will give a little more work day by day to the NEMO Officers which must be balanced with more autonomy. If all goes according to the plan, this evolution will be almost harmless for the users and will make life easier for the developers. The main strategy is to reach a compromise between the different groups with distinct needs and our integrated tools. A predetermined rule of one tool per group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static to prepare its relocation/substitution (no more registration for users nor dynamical content) - Users -> New Forge for Users ("slave" repository + SCM like Trac) * Standalone authentication system (a copy of the existing user accounts is considered) * Own bug tracking system * New complete wiki (a shared work must be carried on this particular topic) - Developers/Contributors -> Existing SVN repository as a "master" repository with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> Current Trac application will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, private wiki, ...). Together a transfer of the present mailing lists from our local IT infrastructure to the hosted service 'Universalistes' by RENATER is planned. It is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address 'news@nemo-ocean.eu' -> No prefix, identified later by '[News]' -> Open access but no posting allowed except from owners i.e. ST via NEMO Officers. - '[nemo_ticket]' will remain a notification list with a custom address 'notification@nemo-ocean.eu' -> Prefix will depend on the triggering action ('[Commit]'|'[Forum]'|'[Ticket]'), identified later by '[Notification]' -> Open access but no posting allowed except notifications from either the IPSL Forge or the new Users Forge. - '[Nemo_st]' will become a confidential list with a hidden address 'systeam@nemo-ocean.eu' -> No prefix, identified later by '[Systeam]' -> Subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket. It will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation.
    to
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE) consisting of: - a website (nemo-ocean.eu) which serves as a public portal - a Forge (forge.ipsl.jussieu.fr/nemo) composed of a SVN repository and a web project management software Trac - 3 mailing lists '[Nemo]', '[nemo_ticket]' & '[Nemo_st]' respectively for the users, the external notification system and the developers community In anticipation of the end of life of the server hosting the website (planned for Q1 2017), I propose a global evolution which will impact all the components but will also remove most of the existing flaws and fill several lacks: - Decentralize the IT system to improve its availability and security - Reduce the duplication and the scattering of the content, and facilitate its edition - Limit the needs for any support or specific development, and simplify the administration tasks To be honest, this will give a little more work day by day to the NEMO Officers which must be balanced with more autonomy. If all goes according to the plan, this evolution will be almost harmless for the users and will make life easier for the developers. The main strategy is to reach a compromise between the different groups with distinct needs and our integrated tools. A predetermined rule of one tool per group brings to the next scheme: - Public -> Current website reduced to its public content (~ static) * No more registration for Forge access (SVN + Trac), nor private content for other groups (i.e 'Users, Developers or ST) * Visitors can always submit publications or associated projects with later validation and contact the webmasters * Only - Users -> New Forge for Users (SVN "slave" repository + Trac-like web application) in the hosted service 'SourceSup' by RENATER (https://sourcesup.renater.fr) * Standalone authentication system: a copy of the existing user accounts is considered, except for pre-registered users from french research network) * Own bug tracking system * New complete wiki (a shared work must be carried on this particular topic) - Developers/Contributors -> Existing SVN repository as a "master" repository with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> Current Trac application will become the only management portal by upgrading its features. Together a transfer of the present mailing lists from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (https://groupes.renater.fr/sympa). It is an opportunity to redefine their object and/or change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address 'news@nemo-ocean.eu', identified later by '[News]' -> No prefix, open access but no posting allowed except from owners i.e. ST via NEMO Officers. - '[nemo_ticket]' will remain a notification list with a custom address 'forge@nemo-ocean.eu', identified later by '[Forge]' -> Prefix will depend on the triggering action ('[Commit]'|'[Forum]'|'[Ticket]'), Open access but no posting allowed except notifications from either the IPSL Forge or the new Users Forge. - '[Nemo_st]' will become a confidential list with a hidden address 'systeam@nemo-ocean.eu', identified later by '[Systeam]', and will be reserved now for internal significant subjects (no more notifications or support) -> No prefix, subscription controlled by NEMO Officers, no external posting. Also a new mailing list 'contact@nemo-ocean.eu', identified later by '[Contact]', will be created for external request or form submission from the website (no support through this) and will include the administrators and the editors of the website (NEMO Officers). In the future, it would mean that anyone who wants to get in touch with us for support will have to open a forum discussion or a ticket in the new Forge. It will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation.

Changed on 2016-06-29T18:13:58+02:00 by nicolasmartin:

Changed on 2016-06-29T18:13:58+02:00 by nicolasmartin:

  • description changed from
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE) consisting of: - a website (nemo-ocean.eu) which serves as a public portal - a Forge (forge.ipsl.jussieu.fr/nemo) composed of a SVN repository and a web project management software Trac - 3 mailing lists '[Nemo]', '[nemo_ticket]' & '[Nemo_st]' respectively for the users, the external notification system and the developers community In anticipation of the end of life of the server hosting the website (planned for Q1 2017), I propose a global evolution which will impact all the components but will also remove most of the existing flaws and fill several lacks: - Decentralize the IT system to improve its availability and security - Reduce the duplication and the scattering of the content, and facilitate its edition - Limit the needs for any support or specific development, and simplify the administration tasks To be honest, this will give a little more work day by day to the NEMO Officers which must be balanced with more autonomy. If all goes according to the plan, this evolution will be almost harmless for the users and will make life easier for the developers. The main strategy is to reach a compromise between the different groups with distinct needs and our integrated tools. A predetermined rule of one tool per group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static to prepare its relocation/substitution (no more registration for users nor dynamical content) - Users -> New Forge for Users ("slave" repository + SCM like Trac) * Standalone authentication system (a copy of the existing user accounts is considered) * Own bug tracking system * New complete wiki (a shared work must be carried on this particular topic) - Developers/Contributors -> Existing SVN repository as a "master" repository with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, poll, personal page, private wiki, ...). Together a transfer of the present mailing lists from our local IT infrastructure to the hosted service 'Universalistes' by RENATER is planned. It is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address 'news@nemo-ocean.eu' -> No prefix, identified later by '[News]' -> Open access but no posting allowed except from owners i.e. ST via NEMO Officers. - '[nemo_ticket]' will remain a notification list with a custom address 'notification@nemo-ocean.eu' -> Prefix will depend on the triggering action ('[Commit]'|'[Forum]'|'[Ticket]'), identified later by '[Notification]' -> Open access but no posting allowed except notifications from either the IPSL Forge or the new Users Forge. - '[Nemo_st]' will become a confidential list with a hidden address 'systeam@nemo-ocean.eu' -> No prefix, identified later by '[Systeam]' -> Subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket. It will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation.
    to
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE) consisting of: - a website (nemo-ocean.eu) which serves as a public portal - a Forge (forge.ipsl.jussieu.fr/nemo) composed of a SVN repository and a web project management software Trac - 3 mailing lists '[Nemo]', '[nemo_ticket]' & '[Nemo_st]' respectively for the users, the external notification system and the developers community In anticipation of the end of life of the server hosting the website (planned for Q1 2017), I propose a global evolution which will impact all the components but will also remove most of the existing flaws and fill several lacks: - Decentralize the IT system to improve its availability and security - Reduce the duplication and the scattering of the content, and facilitate its edition - Limit the needs for any support or specific development, and simplify the administration tasks To be honest, this will give a little more work day by day to the NEMO Officers which must be balanced with more autonomy. If all goes according to the plan, this evolution will be almost harmless for the users and will make life easier for the developers. The main strategy is to reach a compromise between the different groups with distinct needs and our integrated tools. A predetermined rule of one tool per group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static to prepare its relocation/substitution (no more registration for users nor dynamical content) - Users -> New Forge for Users ("slave" repository + SCM like Trac) * Standalone authentication system (a copy of the existing user accounts is considered) * Own bug tracking system * New complete wiki (a shared work must be carried on this particular topic) - Developers/Contributors -> Existing SVN repository as a "master" repository with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> Current Trac application will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, private wiki, ...). Together a transfer of the present mailing lists from our local IT infrastructure to the hosted service 'Universalistes' by RENATER is planned. It is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address 'news@nemo-ocean.eu' -> No prefix, identified later by '[News]' -> Open access but no posting allowed except from owners i.e. ST via NEMO Officers. - '[nemo_ticket]' will remain a notification list with a custom address 'notification@nemo-ocean.eu' -> Prefix will depend on the triggering action ('[Commit]'|'[Forum]'|'[Ticket]'), identified later by '[Notification]' -> Open access but no posting allowed except notifications from either the IPSL Forge or the new Users Forge. - '[Nemo_st]' will become a confidential list with a hidden address 'systeam@nemo-ocean.eu' -> No prefix, identified later by '[Systeam]' -> Subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket. It will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation.

Changed on 2016-06-28T21:18:05+02:00 by nicolasmartin:

Changed on 2016-06-28T21:18:05+02:00 by nicolasmartin:

  • description changed from
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE) consisting of: - a website (nemo-ocean.eu) which serves as a public portal - a Forge (forge.ipsl.jussieu.fr/nemo) composed of a SVN repository and a web project management software Trac - 3 mailing lists '[Nemo]', '[nemo_ticket]' & '[Nemo_st]' respectively for the users, the external notification system and the developers community In anticipation of the end of life of the server hosting the website (planned for Q1 2017), I propose a global evolution which will impact all the components but will also remove most of the existing flaws and fill several lacks: - Decentralize the IT system to improve its availability and security - Reduce the duplication and the scattering of the content, and facilitate its edition - Limit the needs for any support or specific development, and simplify the administration tasks To be honest, this will give a little more work day by day to the NEMO Officers which must be balanced with more autonomy. If all goes according to the plan, this evolution will be almost harmless for the users and will make life easier for the developers. The main strategy is to reach a compromise between the different groups with distinct needs and our integrated tools. A predetermined rule of one tool per group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static to prepare its relocation/substitution (no more registration for users nor dynamical content) - Users -> New Forge for Users ("slave" repository + SCM like Trac) * Standalone authentication system (a copy of the existing user accounts is considered) * Own bug tracking system * New complete wiki (a shared work must be carried on this particular topic) - Developers/Contributors -> Existing SVN repository as a "master" repository with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, poll, personal page, private wiki, ...). Together a transfer of the present mailing lists from our local IT infrastructure to the hosted service 'Universalistes' by RENATER is planned. It is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address 'news@nemo-ocean.eu' and no prefix (identified later by '[News]' ) -> Open access but no posting allowed except from owners i.e. ST via NEMO Officers. - '[nemo_ticket]' will remain a notification list "" " "" " 'notification@nemo-ocean.eu' " "" "" ( "" " "" '[Notification]') -> "" "" " "" " " "" notifications from either the IPSL Forge or the new Users Forge. - '[Nemo_st]' "" "" " confidential list "" " hidden " 'systeam@nemo-ocean.eu' " "" "" ( "" " "" '[Systeam]' ) -> Subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket. It will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation.
    to
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE) consisting of: - a website (nemo-ocean.eu) which serves as a public portal - a Forge (forge.ipsl.jussieu.fr/nemo) composed of a SVN repository and a web project management software Trac - 3 mailing lists '[Nemo]', '[nemo_ticket]' & '[Nemo_st]' respectively for the users, the external notification system and the developers community In anticipation of the end of life of the server hosting the website (planned for Q1 2017), I propose a global evolution which will impact all the components but will also remove most of the existing flaws and fill several lacks: - Decentralize the IT system to improve its availability and security - Reduce the duplication and the scattering of the content, and facilitate its edition - Limit the needs for any support or specific development, and simplify the administration tasks To be honest, this will give a little more work day by day to the NEMO Officers which must be balanced with more autonomy. If all goes according to the plan, this evolution will be almost harmless for the users and will make life easier for the developers. The main strategy is to reach a compromise between the different groups with distinct needs and our integrated tools. A predetermined rule of one tool per group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static to prepare its relocation/substitution (no more registration for users nor dynamical content) - Users -> New Forge for Users ("slave" repository + SCM like Trac) * Standalone authentication system (a copy of the existing user accounts is considered) * Own bug tracking system * New complete wiki (a shared work must be carried on this particular topic) - Developers/Contributors -> Existing SVN repository as a "master" repository with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, poll, personal page, private wiki, ...). Together a transfer of the present mailing lists from our local IT infrastructure to the hosted service 'Universalistes' by RENATER is planned. It is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address 'news@nemo-ocean.eu' -> No prefix, identified later by '[News]' -> Open access but no posting allowed except from owners i.e. ST via NEMO Officers. - '[nemo_ticket]' will remain a notification list with a custom address 'notification@nemo-ocean.eu' -> Prefix will depend on the triggering action ('[Commit]'|'[Forum]'|'[Ticket]'), identified later by '[Notification]' -> Open access but no posting allowed except notifications from either the IPSL Forge or the new Users Forge. - '[Nemo_st]' will become a confidential list with a hidden address 'systeam@nemo-ocean.eu' -> No prefix, identified later by '[Systeam]' -> Subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket. It will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation.

Changed on 2016-06-28T20:52:47+02:00 by nicolasmartin:

Changed on 2016-06-28T20:52:47+02:00 by nicolasmartin:

  • description changed from
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE) consisting of: - a website (nemo-ocean.eu) which serves as a public portal - a Forge (forge.ipsl.jussieu.fr/nemo) composed of a SVN repository and a web project management software Trac - 2 mailing lists '[Nemo]' & '[Nemo_st]' respectively for the users and the developers community In anticipation of the end of life of the server hosting the website (planned for Q1 2017), I propose a global evolution which will impact all the components but will also remove most of the existing flaws and fill several lacks: - Decentralize the IT system to improve its availability and security - Reduce the duplication and the scattering of the content, and facilitate its edition - Limit the needs for any support or specific development, and simplify the administration tasks To be honest, this will give a little more work day by day to the NEMO Officers which must be balanced with more autonomy. If all goes according to the plan, this evolution will be almost harmless for the users and will make life easier for the developers. The main strategy is to reach a compromise between the different groups with distinct needs and our integrated tools. A predetermined rule of one tool per group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static to prepare its relocation/substitution (no more registration for users nor dynamical content) - Users -> New Forge for Users ("slave" repository + SCM like Trac) * Standalone authentication system (a copy of the existing user accounts is considered) * Own bug tracking system * New complete wiki (a shared work must be carried on this particular topic) - Developers/Contributors -> Existing SVN repository as a "master" repository with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, poll, personal page, private wiki, ...). Together a transfer of the present mailing lists from our local IT infrastructure to the hosted service 'Universalistes' by RENATER is planned. It is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address 'news@nemo-ocean.eu' and no prefix (identified later by '[News]' ) -> Open access but no posting allowed expect from owners i.e. ST via NEMO Officers. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" 'systeam@nemo-ocean.eu' " "" "" ( "" " "" '[Systeam]') -> Subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket. It will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation.
    to
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE) consisting of: - a website (nemo-ocean.eu) which serves as a public portal - a Forge (forge.ipsl.jussieu.fr/nemo) composed of a SVN repository and a web project management software Trac - 3 mailing lists '[Nemo]', '[nemo_ticket]' & '[Nemo_st]' respectively for the users, the external notification system and the developers community In anticipation of the end of life of the server hosting the website (planned for Q1 2017), I propose a global evolution which will impact all the components but will also remove most of the existing flaws and fill several lacks: - Decentralize the IT system to improve its availability and security - Reduce the duplication and the scattering of the content, and facilitate its edition - Limit the needs for any support or specific development, and simplify the administration tasks To be honest, this will give a little more work day by day to the NEMO Officers which must be balanced with more autonomy. If all goes according to the plan, this evolution will be almost harmless for the users and will make life easier for the developers. The main strategy is to reach a compromise between the different groups with distinct needs and our integrated tools. A predetermined rule of one tool per group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static to prepare its relocation/substitution (no more registration for users nor dynamical content) - Users -> New Forge for Users ("slave" repository + SCM like Trac) * Standalone authentication system (a copy of the existing user accounts is considered) * Own bug tracking system * New complete wiki (a shared work must be carried on this particular topic) - Developers/Contributors -> Existing SVN repository as a "master" repository with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, poll, personal page, private wiki, ...). Together a transfer of the present mailing lists from our local IT infrastructure to the hosted service 'Universalistes' by RENATER is planned. It is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address 'news@nemo-ocean.eu' and no prefix (identified later by '[News]' ) -> Open access but no posting allowed except from owners i.e. ST via NEMO Officers. - '[nemo_ticket]' will remain a notification list "" " "" " 'notification@nemo-ocean.eu' " "" "" ( "" " "" '[Notification]') -> "" "" " "" " " "" notifications from either the IPSL Forge or the new Users Forge. - '[Nemo_st]' "" "" " confidential list "" " hidden " 'systeam@nemo-ocean.eu' " "" "" ( "" " "" '[Systeam]' ) -> Subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket. It will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation.

Changed on 2016-06-02T17:07:25+02:00 by nicolasmartin:

Changed on 2016-06-02T17:07:25+02:00 by nicolasmartin:

  • pi changed from
    Nicolas MARTIN
    to
    Nicolas MARTIN & Mathieu Peltier

Changed on 2016-03-21T18:43:02+01:00 by nicolasmartin:

Changed on 2016-03-21T18:43:02+01:00 by nicolasmartin:

  • description changed from
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE) consisting of: - a website (nemo-ocean.eu) which serves as a public portal - a Forge (forge.ipsl.jussieu.fr/nemo) composed of a SVN repository and a web project management software Trac - 2 mailing lists '[Nemo]' & '[Nemo_st]' respectively for the users and the developers community In anticipation of the end of life of the server hosting the website (planned for Q1 2017), I propose a global evolution which will impact all the components but will also remove most of the existing flaws and fill several lacks: - Decentralize the IT system to improve its availability and security - Reduce the duplication and the scattering of the content, and facilitate its edition - Limit the needs for any support or specific development, and simplify the administration tasks To be honest, this will give a little more work day by day to the NEMO Officers which must be balanced with more autonomy. If all goes according to the plan, this evolution will be almost harmless for the users and will make life easier for the developers. The main strategy is to reach a compromise between the different groups with distinct needs and our integrated tools. A predetermined rule of one tool per group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static to prepare its relocation/substitution (no more registration for users nor dynamical content) - Users -> New Forge for Users ("slave" repository + SCM like Trac) * Standalone authentication system (a copy of the existing user accounts is considered) * Own bug tracking system * New completely wiki (a shared work must be carried on this particular topic) - Developers/Contributors -> Existing SVN repository as a "master" repository with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, poll, personal page, private wiki, ...). Together a transfer of the present mailing lists from our local IT infrastructure to the hosted service 'Universalistes' by RENATER is planned. It is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address 'news@nemo-ocean.eu' and no prefix (identified later by '[News]' ) -> Open access but no posting allowed expect from owners i.e. ST via NEMO Officers. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" 'systeam@nemo-ocean.eu' " "" "" ( "" " "" '[Systeam]') -> Subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket. It will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation.
    to
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE) consisting of: - a website (nemo-ocean.eu) which serves as a public portal - a Forge (forge.ipsl.jussieu.fr/nemo) composed of a SVN repository and a web project management software Trac - 2 mailing lists '[Nemo]' & '[Nemo_st]' respectively for the users and the developers community In anticipation of the end of life of the server hosting the website (planned for Q1 2017), I propose a global evolution which will impact all the components but will also remove most of the existing flaws and fill several lacks: - Decentralize the IT system to improve its availability and security - Reduce the duplication and the scattering of the content, and facilitate its edition - Limit the needs for any support or specific development, and simplify the administration tasks To be honest, this will give a little more work day by day to the NEMO Officers which must be balanced with more autonomy. If all goes according to the plan, this evolution will be almost harmless for the users and will make life easier for the developers. The main strategy is to reach a compromise between the different groups with distinct needs and our integrated tools. A predetermined rule of one tool per group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static to prepare its relocation/substitution (no more registration for users nor dynamical content) - Users -> New Forge for Users ("slave" repository + SCM like Trac) * Standalone authentication system (a copy of the existing user accounts is considered) * Own bug tracking system * New complete wiki (a shared work must be carried on this particular topic) - Developers/Contributors -> Existing SVN repository as a "master" repository with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, poll, personal page, private wiki, ...). Together a transfer of the present mailing lists from our local IT infrastructure to the hosted service 'Universalistes' by RENATER is planned. It is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address 'news@nemo-ocean.eu' and no prefix (identified later by '[News]' ) -> Open access but no posting allowed expect from owners i.e. ST via NEMO Officers. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" 'systeam@nemo-ocean.eu' " "" "" ( "" " "" '[Systeam]') -> Subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket. It will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation.

Changed on 2016-03-15T20:39:12+01:00 by nicolasmartin:

Changed on 2016-03-15T20:39:12+01:00 by nicolasmartin:

  • implementation changed from
    This evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last. At this stage, I emphasize on the shared work that will have to be done on the Users Forge. From the content of the users area in the website, we need probably to redefine and reconsider it for the making of the new wiki for users. The schedule is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Independent operations on components with no external interference (few weeks) - Website (no particular operation scheduled) * Users still allowed to register and get access to the IPSL Forge (repository and Trac) * New collaborative ST work move to IPSL Trac (agenda, reports, document design & sharing, wikis, ...) - IPSL Trac * NEMO officers appointed as permissions administrator in order to manage their own developers within their institute * Complete by an internal script the Trac profiles from the informations of their IPSL Forge account (name & email) * Replace the global notification for '[Nemo_st]' (wiki and ticket updates) by a customizable system with 2 plugins # Allow the subscription for an email notification of wiki page updates. Sender: 'Trac Wiki Notification <nemo@forge.ipsl.jussieu.fr>', Prefix: '[Wiki]' # Ticket creation & resolution notified to all i.e ST Others modifications notified only to the reporter, the owner and the 'Cc'ers of the ticket Sender: 'Trac Ticket Notification <nemo@forge.ipsl.jussieu.fr>', Prefix: '[Ticket]' - IPSL Forge: NEMO officers appointed as project administrators in order to manage their own developers within their institute - IPSL repository: replace the global notification sending (commits) to '[Nemo_st]' by an internal script which will update the local mailing list every 30 mns from developers group. Sender: 'SVN Commit Notification <nemo@forge.ipsl.jussieu.fr>', Prefix: '[Commit]' - Mailing lists * Create a CRU ("Compte Réseau Universel") account for each NEMO Officer to access the RENATER network * "" '[News]' & '[Systeam]' on 'Universalistes' with Officers as owners 2) Establishment of the Users Forge (2 to 3 months) - Website: enable for a new user the subscription to '[News]' in addition of '[Nemo]' - Users Forge (offline or hidden) * Initialise the new repository and the replication from IPSL repository, then monitor the synchronization * Configure the new SCM (bug tracking system, forum, wiki, ...) * Transfer and update user content from the website: user guides, reference configurations pages, FAQ & utilities * Investigate the possibility of versionning the new wiki pages with the code repository - Mailing lists * Copy the missing members of '[News]' from '[Nemo]' * Begin to use '[News]' & '[Systeam]' and keep '[Nemo]' & '[Nemo_st]' for external requests. 3) Critical switch of NEMO Users to the new architecture (1~2 whole days for operation) - Website (offline during the process) * Block registration of a new user and turn off the synchronization of the accounts to IPSL Forge. * Private areas will be only accessible to ST for reading. * User connection will not open access to more content i.e public site. * Edit accordingly the public pages regarding the new architecture. - IPSL Forge (online): remove access of the website accounts - IPSL Trac: review default permissions for basic user (merge 'developer' & 'authenticated' role) - Users Forge (online after website maintenance): * Recover the up-to-date accounts database from website * Open access to previous members from website with the same ID (login/passwd) - Mailing lists * Close '[Nemo]', '[Nemo_st]' & '[nemo_ticket]'. * De facto '[News]' & '[Systeam]' will become the ones to use. 4) Get ready for the EOL of website server (target Q1 2017) With the previous work done which will reduced the dependency with the other components (less content to manage and no external constraint), We can choose freely between 2 solutions: - simply copy the current website on a new server (easiest) - completely revise the website with a more user-friendly SCM and a pleasant design (needed)
    to
    This evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last. At this stage, I emphasize on the shared work that will have to be done on the Users Forge. From the content of the users area in the website, we need probably to redefine and reconsider it for the making of the new wiki for users. The schedule is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Independent operations on components with no external interference (few weeks) - Website (no particular operation scheduled) * Users still allowed to register and get access to the IPSL Forge (repository and Trac) * New collaborative ST work move to IPSL Trac (agenda, reports, document design & sharing, wikis, ...) - IPSL Trac * NEMO officers appointed as permissions administrator in order to manage their own developers within their institute * Complete by an internal script the Trac profiles from the informations of their IPSL Forge account (name & email) * Replace the global notification for '[Nemo_st]' (wiki and ticket updates) by a customizable system with 2 plugins # Allow the subscription for an email notification of wiki page updates. Sender: 'Trac Wiki Notification <nemo@forge.ipsl.jussieu.fr>', Prefix: '[Wiki]' # Ticket creation & resolution notified to all i.e ST Others modifications notified only to the reporter, the owner and the 'Cc'ers of the ticket Sender: 'Trac Ticket Notification <nemo@forge.ipsl.jussieu.fr>', Prefix: '[Ticket]' - IPSL Forge: NEMO officers appointed as project administrators in order to manage their own developers within their institute - IPSL repository: replace the global notification sending (commits) to '[Nemo_st]' by an internal script which will update the local mailing list every 30 mns from developers group. Sender: 'SVN Commit Notification <nemo@forge.ipsl.jussieu.fr>', Prefix: '[Commit]' - Mailing lists * Create a CRU ("Compte Réseau Universel") account for each NEMO Officer to access the RENATER network * "" '[News]' & '[Systeam]' on 'Universalistes' with Officers as owners 2) Establishment of the Users Forge (2 to 3 months) - Website: enable for a new user the subscription to '[News]' in addition of '[Nemo]' - Users Forge (offline or hidden) * Initialise the new repository and the replication from IPSL repository, then monitor the synchronization * Configure the new SCM (bug tracking system, forum, wiki, ...) * Transfer and update user content from the website: user guides, reference configurations pages, FAQ & utilities * Investigate the possibility of versionning the new wiki pages with the code repository - Mailing lists * Copy the missing members of '[News]' from '[Nemo]' * Begin to use '[News]' & '[Systeam]' and keep '[Nemo]' & '[Nemo_st]' for external requests. 3) Critical switch of NEMO Users to the new architecture (1~2 whole days for operation) - Website (offline during the process) * Block registration of a new user and turn off the synchronization of the accounts to IPSL Forge. * Private areas will be only accessible to ST for reading. * User connection will not open access to more content i.e public site. * Edit accordingly the public pages regarding the new architecture. - IPSL Forge (online): remove access of the website accounts - IPSL Trac: review default permissions for basic user (merge 'developer' & 'authenticated' role) - Users Forge (online after website maintenance): * Recover the up-to-date accounts database from website * Open access to previous members from website with the same ID (login/passwd) - Mailing lists * Close '[Nemo]', '[Nemo_st]' & '[nemo_ticket]'. * De facto '[News]' & '[Systeam]' will become the ones to use. 4) Get ready for the EOL of website server (target Q1 2017) With the previous work done which will reduced the dependency with the other components (less content to manage and no external constraint), We can choose freely between 2 solutions: - simply copy the current website on a new server (easiest) - completely revise the website with a more user-friendly SCM and a pleasant design (needed)

Changed on 2016-03-15T20:35:01+01:00 by nicolasmartin:

Changed on 2016-03-15T20:35:01+01:00 by nicolasmartin:

  • implementation changed from
    alThis evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last. The schedule is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Independent operations on components with no external interference (few weeks) - Website (no particular operation scheduled) * Users still allowed to register and get access to the IPSL Forge (repository and Trac) * New collaborative ST work move to IPSL Trac (agenda, reports, document design & sharing, wikis, ...) - IPSL Trac * NEMO officers appointed as permissions administrator in order to manage their own developers within their institute * Complete by an internal script the Trac profiles from the informations of their IPSL Forge account (name & email) * Replace the global notification for '[Nemo_st]' (wiki and ticket updates) by a customizable system with 2 plugins # Allow the subscription for an email notification of wiki page updates. Sender: 'Trac Wiki Notification <nemo@forge.ipsl.jussieu.fr>', Prefix: '[Wiki]' # Ticket creation & resolution notified to all i.e ST Others modifications notified only to the reporter, the owner and the 'Cc'ers of the ticket Sender: 'Trac Ticket Notification <nemo@forge.ipsl.jussieu.fr>', Prefix: '[Ticket]' - IPSL Forge: NEMO officers appointed as project administrators in order to manage their own developers within their institute - IPSL repository: replace the global notification sending (commits) to '[Nemo_st]' by an internal script which will update the local mailing list every 30 mns from developers group. Sender: 'SVN Commit Notification <nemo@forge.ipsl.jussieu.fr>', Prefix: '[Commit]' - Mailing lists * Create a CRU ("Compte Réseau Universel") account for each NEMO Officer to access the RENATER network * "" '[News]' & '[Systeam]' on 'Universalistes' with Officers as owners 2) Establishment of the Users Forge (2 to 3 months) - Website: enable for a new user the subscription to '[News]' in addition of '[Nemo]' - Users Forge (offline or hidden) * Initialise the new repository and the replication from IPSL repository, then monitor the synchronization * Configure the new SCM (bug tracking system, forum, wiki, ...) * Transfer and update user content from the website: user guides, reference configurations pages, FAQ & utilities * Investigate the possibility of versionning the new wiki pages with the code repository - Mailing lists * Copy the missing members of '[News]' from '[Nemo]' * Begin to use '[News]' & '[Systeam]' and keep '[Nemo]' & '[Nemo_st]' for external requests. 3) Critical switch of NEMO Users to the new architecture (1~2 whole days for operation) - Website (offline during the process) * Block registration of a new user and turn off the synchronization of the accounts to IPSL Forge * Private areas will be only accessible to ST, user connection will not open access to more content than public site. * Edit accordingly the public pages regarding the new architecture - IPSL Forge (online): remove access of the website accounts - IPSL Trac: review default permissions for basic user (merge 'developer' & 'authenticated' role) - Users Forge (online after website maintenance): * Recover the up-to-date accounts database from website * Open access to previous members from website with the same ID (login/passwd) - Mailing lists * Close '[Nemo]', '[Nemo_st]' & '[nemo_ticket]'. * De facto '[News]' & '[Systeam]' will become the ones to use. 4) Get ready for the EOL of website server (target Q1 2017) With the previous work done which will reduced the dependency with the other components (less content to manage and no external constraint), We can choose freely between 2 solutions: - simply copy the current website on a new server (easiest) - completely revise the website with a more user-friendly SCM and a pleasant design (needed)
    to
    This evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last. At this stage, I emphasize on the shared work that will have to be done on the Users Forge. From the content of the users area in the website, we need probably to redefine and reconsider it for the making of the new wiki for users. The schedule is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Independent operations on components with no external interference (few weeks) - Website (no particular operation scheduled) * Users still allowed to register and get access to the IPSL Forge (repository and Trac) * New collaborative ST work move to IPSL Trac (agenda, reports, document design & sharing, wikis, ...) - IPSL Trac * NEMO officers appointed as permissions administrator in order to manage their own developers within their institute * Complete by an internal script the Trac profiles from the informations of their IPSL Forge account (name & email) * Replace the global notification for '[Nemo_st]' (wiki and ticket updates) by a customizable system with 2 plugins # Allow the subscription for an email notification of wiki page updates. Sender: 'Trac Wiki Notification <nemo@forge.ipsl.jussieu.fr>', Prefix: '[Wiki]' # Ticket creation & resolution notified to all i.e ST Others modifications notified only to the reporter, the owner and the 'Cc'ers of the ticket Sender: 'Trac Ticket Notification <nemo@forge.ipsl.jussieu.fr>', Prefix: '[Ticket]' - IPSL Forge: NEMO officers appointed as project administrators in order to manage their own developers within their institute - IPSL repository: replace the global notification sending (commits) to '[Nemo_st]' by an internal script which will update the local mailing list every 30 mns from developers group. Sender: 'SVN Commit Notification <nemo@forge.ipsl.jussieu.fr>', Prefix: '[Commit]' - Mailing lists * Create a CRU ("Compte Réseau Universel") account for each NEMO Officer to access the RENATER network * "" '[News]' & '[Systeam]' on 'Universalistes' with Officers as owners 2) Establishment of the Users Forge (2 to 3 months) - Website: enable for a new user the subscription to '[News]' in addition of '[Nemo]' - Users Forge (offline or hidden) * Initialise the new repository and the replication from IPSL repository, then monitor the synchronization * Configure the new SCM (bug tracking system, forum, wiki, ...) * Transfer and update user content from the website: user guides, reference configurations pages, FAQ & utilities * Investigate the possibility of versionning the new wiki pages with the code repository - Mailing lists * Copy the missing members of '[News]' from '[Nemo]' * Begin to use '[News]' & '[Systeam]' and keep '[Nemo]' & '[Nemo_st]' for external requests. 3) Critical switch of NEMO Users to the new architecture (1~2 whole days for operation) - Website (offline during the process) * Block registration of a new user and turn off the synchronization of the accounts to IPSL Forge. * Private areas will be only accessible to ST for reading. * User connection will not open access to more content i.e public site. * Edit accordingly the public pages regarding the new architecture. - IPSL Forge (online): remove access of the website accounts - IPSL Trac: review default permissions for basic user (merge 'developer' & 'authenticated' role) - Users Forge (online after website maintenance): * Recover the up-to-date accounts database from website * Open access to previous members from website with the same ID (login/passwd) - Mailing lists * Close '[Nemo]', '[Nemo_st]' & '[nemo_ticket]'. * De facto '[News]' & '[Systeam]' will become the ones to use. 4) Get ready for the EOL of website server (target Q1 2017) With the previous work done which will reduced the dependency with the other components (less content to manage and no external constraint), We can choose freely between 2 solutions: - simply copy the current website on a new server (easiest) - completely revise the website with a more user-friendly SCM and a pleasant design (needed)
  • description changed from
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE) consisting of: - a website (nemo-ocean.eu) which serves as a public portal - a Forge (forge.ipsl.jussieu.fr/nemo) composed of a SVN repository and a web project management software Trac - 2 mailing lists '[Nemo]' & '[Nemo_st]' respectively for the users and the developers community In anticipation of the end of life of the server hosting the website (planned for Q1 2017), I propose a global evolution which will impact all components but will also remove most of the existing flaws and fill several lacks: - Decentralize the IT system to improve its availability and security - Reduce the duplication and the scattering of the content, and facilitate its edition - Limit the needs for any support or specific development, and simplify the administration tasks To be honest, this will give a little more work day by day to the NEMO Officers which must be balanced with more autonomy. The main strategy is to reach a compromise between different groups with specific needs and integrated tools. A predetermined rule of one tool per group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static to prepare its relocation/substitution (no more registration for users nor dynamical content) - Users -> New Forge for Users ("slave" repository + SCM like Trac) * Standalone authentication system (a copy of the existing user accounts is considered) * Own bug tracking system * New completely wiki (a shared work must be carried on this particular topic) - Developers/Contributors -> Existing SVN repository as a "master" repository with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, poll, personal page, private wiki, ...). Together a transfer of the present mailing lists from our local IT infrastructure to the hosted service 'Universalistes' by RENATER is planned. It is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address 'news@nemo-ocean.eu' and no prefix (identified later by '[News]' ) -> Open access but no posting allowed expect from owners i.e. ST via NEMO Officers. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" 'systeam@nemo-ocean.eu' " "" "" ( "" " "" '[Systeam]') -> Subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket. It will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation.
    to
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE) consisting of: - a website (nemo-ocean.eu) which serves as a public portal - a Forge (forge.ipsl.jussieu.fr/nemo) composed of a SVN repository and a web project management software Trac - 2 mailing lists '[Nemo]' & '[Nemo_st]' respectively for the users and the developers community In anticipation of the end of life of the server hosting the website (planned for Q1 2017), I propose a global evolution which will impact all the components but will also remove most of the existing flaws and fill several lacks: - Decentralize the IT system to improve its availability and security - Reduce the duplication and the scattering of the content, and facilitate its edition - Limit the needs for any support or specific development, and simplify the administration tasks To be honest, this will give a little more work day by day to the NEMO Officers which must be balanced with more autonomy. If all goes according to the plan, this evolution will be almost harmless for the users and will make life easier for the developers. The main strategy is to reach a compromise between the different groups with distinct needs and our integrated tools. A predetermined rule of one tool per group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static to prepare its relocation/substitution (no more registration for users nor dynamical content) - Users -> New Forge for Users ("slave" repository + SCM like Trac) * Standalone authentication system (a copy of the existing user accounts is considered) * Own bug tracking system * New completely wiki (a shared work must be carried on this particular topic) - Developers/Contributors -> Existing SVN repository as a "master" repository with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, poll, personal page, private wiki, ...). Together a transfer of the present mailing lists from our local IT infrastructure to the hosted service 'Universalistes' by RENATER is planned. It is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address 'news@nemo-ocean.eu' and no prefix (identified later by '[News]' ) -> Open access but no posting allowed expect from owners i.e. ST via NEMO Officers. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" 'systeam@nemo-ocean.eu' " "" "" ( "" " "" '[Systeam]') -> Subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket. It will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation.

Changed on 2016-03-15T19:41:30+01:00 by nicolasmartin:

Changed on 2016-03-15T19:41:30+01:00 by nicolasmartin:

  • description changed from
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE) consisting of: - a website (nemo-ocean.eu) which serves as a public portal - a Forge (forge.ipsl.jussieu.fr/nemo) composed of a SVN repository and a web project management software Trac - 2 mailing lists '[Nemo]' & '[Nemo_st]' respectively for the users and the developers community In anticipation of the end of life of the server hosting the website (planned for Q1 2017), I propose a global evolution which will impact all components but will also remove most of the existing flaws and fill several lacks: - Decentralize the IT system to improve its availability and security - Reduce the duplication and the scattering of the content, and facilitate its edition - Limit the needs for support or specific development, and simplify the administration tasks To be honest, this will give a little more work day by day to the NEMO Officers which must be balanced with more autonomy. The main strategy is to reach a compromise between different groups with specific needs and integrated tools. A predetermined rule of one tool for one group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static No more registration for users nor dynamical content to prepare its relocation/substitution - Users -> New Forge for Users (repository + SCM) * Standalone authentication system (a copy of the existing user accounts is considered) * Own bug tracking system * New wiki - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, poll, personal page, private wiki, ...). Together a transfer of the present mailing lists from our local IT infrastructure to the hosted service 'Universalistes' by RENATER is planned. It is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address 'news@nemo-ocean.eu' and no prefix (identified later by '[News]' ) -> Open access but no posting allowed expect from owners i.e. ST via NEMO Officers. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" 'systeam@nemo-ocean.eu' " "" "" ( "" " "" '[Systeam]') -> Subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket. It will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation.
    to
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE) consisting of: - a website (nemo-ocean.eu) which serves as a public portal - a Forge (forge.ipsl.jussieu.fr/nemo) composed of a SVN repository and a web project management software Trac - 2 mailing lists '[Nemo]' & '[Nemo_st]' respectively for the users and the developers community In anticipation of the end of life of the server hosting the website (planned for Q1 2017), I propose a global evolution which will impact all components but will also remove most of the existing flaws and fill several lacks: - Decentralize the IT system to improve its availability and security - Reduce the duplication and the scattering of the content, and facilitate its edition - Limit the needs for any support or specific development, and simplify the administration tasks To be honest, this will give a little more work day by day to the NEMO Officers which must be balanced with more autonomy. The main strategy is to reach a compromise between different groups with specific needs and integrated tools. A predetermined rule of one tool per group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static to prepare its relocation/substitution (no more registration for users nor dynamical content) - Users -> New Forge for Users ("slave" repository + SCM like Trac) * Standalone authentication system (a copy of the existing user accounts is considered) * Own bug tracking system * New completely wiki (a shared work must be carried on this particular topic) - Developers/Contributors -> Existing SVN repository as a "master" repository with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, poll, personal page, private wiki, ...). Together a transfer of the present mailing lists from our local IT infrastructure to the hosted service 'Universalistes' by RENATER is planned. It is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address 'news@nemo-ocean.eu' and no prefix (identified later by '[News]' ) -> Open access but no posting allowed expect from owners i.e. ST via NEMO Officers. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" 'systeam@nemo-ocean.eu' " "" "" ( "" " "" '[Systeam]') -> Subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket. It will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation.

Changed on 2016-03-15T19:25:05+01:00 by nicolasmartin:

Changed on 2016-03-15T19:25:05+01:00 by nicolasmartin:

  • implementation changed from
    This evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last. The schedule is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Independent operations on components with no external interference (few weeks) - Website (no particular operation scheduled) * Users still allowed to register and get access to the IPSL Forge (repository and Trac) * New collaborative ST work move to IPSL Trac (agenda, reports, document design & sharing, wikis, ...) - IPSL Trac * NEMO officers appointed as permissions administrator in order to manage their own developers within their institute * Complete by an internal script the Trac profiles from the informations of their IPSL Forge account (name & email) * Replace the global notification for '[Nemo_st]' (wiki and ticket updates) by a customizable system with 2 plugins # Allow the subscription for an email notification of wiki page updates. Sender: 'Trac Wiki Notification <nemo@forge.ipsl.jussieu.fr>', Prefix: '[Wiki]' # Ticket creation & resolution notified to all i.e ST Others modifications notified only to the reporter, the owner and the 'Cc'ers of the ticket Sender: 'Trac Ticket Notification <nemo@forge.ipsl.jussieu.fr>', Prefix: '[Ticket]' - IPSL Forge: NEMO officers appointed as project administrators in order to manage their own developers within their institute - IPSL repository: replace the global notification sending (commits) to '[Nemo_st]' by an internal script which will update the local mailing list every 30 mns from developers group. Sender: 'SVN Commit Notification <nemo@forge.ipsl.jussieu.fr>', Prefix: '[Commit]' - Mailing lists * Create a CRU ("Compte Réseau Universel") account for each NEMO Officer to access the RENATER network * "" '[News]' & '[Systeam]' on 'Universalistes' with Officers as owners 2) Establishment of the Users Forge (2 to 3 months) - Website: enable for a new user the subscription to '[News]' in addition of '[Nemo]' - Users Forge (offline or hidden) * Initialise the new repository and the replication from IPSL repository, then monitor the synchronization * Configure the new SCM (bug tracking system, forum, wiki, ...) * Transfer and update user content from the website: user guides, reference configurations pages, FAQ & utilities * Investigate the possibility of versionning the new wiki pages with the code repository - Mailing lists * Copy the missing members of '[News]' from '[Nemo]' * Begin to use '[News]' & '[Systeam]' and keep '[Nemo]' & '[Nemo_st]' for external requests. 3) Critical switch of NEMO Users to the new architecture (1~2 whole days for operation) - Website (offline during the process) * Block registration of a new user and turn off the synchronization of the accounts to IPSL Forge * Private areas will be only accessible to ST, user connection will not open access to more content than public site. * Edit accordingly the public pages regarding the new architecture - IPSL Forge (online): remove access of the website accounts - IPSL Trac: review default permissions for basic user (merge 'developer' & 'authenticated' role) - Users Forge (online after website maintenance): * Recover the up-to-date accounts database from website * Open access to previous members from website with the same ID (login/passwd) - Mailing lists * Close '[Nemo]', '[Nemo_st]' & '[nemo_ticket]'. * De facto '[News]' & '[Systeam]' will become the ones to use. 4) Get ready for the EOL of website server (target Q1 2017) With the previous work done which will reduced the dependency with the other components (less content to manage and no external constraint), We can choose freely between 2 solutions: - simply copy the current website on a new server (easiest) - completely revise the website with a more user-friendly SCM and a pleasant design (needed)
    to
    alThis evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last. The schedule is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Independent operations on components with no external interference (few weeks) - Website (no particular operation scheduled) * Users still allowed to register and get access to the IPSL Forge (repository and Trac) * New collaborative ST work move to IPSL Trac (agenda, reports, document design & sharing, wikis, ...) - IPSL Trac * NEMO officers appointed as permissions administrator in order to manage their own developers within their institute * Complete by an internal script the Trac profiles from the informations of their IPSL Forge account (name & email) * Replace the global notification for '[Nemo_st]' (wiki and ticket updates) by a customizable system with 2 plugins # Allow the subscription for an email notification of wiki page updates. Sender: 'Trac Wiki Notification <nemo@forge.ipsl.jussieu.fr>', Prefix: '[Wiki]' # Ticket creation & resolution notified to all i.e ST Others modifications notified only to the reporter, the owner and the 'Cc'ers of the ticket Sender: 'Trac Ticket Notification <nemo@forge.ipsl.jussieu.fr>', Prefix: '[Ticket]' - IPSL Forge: NEMO officers appointed as project administrators in order to manage their own developers within their institute - IPSL repository: replace the global notification sending (commits) to '[Nemo_st]' by an internal script which will update the local mailing list every 30 mns from developers group. Sender: 'SVN Commit Notification <nemo@forge.ipsl.jussieu.fr>', Prefix: '[Commit]' - Mailing lists * Create a CRU ("Compte Réseau Universel") account for each NEMO Officer to access the RENATER network * "" '[News]' & '[Systeam]' on 'Universalistes' with Officers as owners 2) Establishment of the Users Forge (2 to 3 months) - Website: enable for a new user the subscription to '[News]' in addition of '[Nemo]' - Users Forge (offline or hidden) * Initialise the new repository and the replication from IPSL repository, then monitor the synchronization * Configure the new SCM (bug tracking system, forum, wiki, ...) * Transfer and update user content from the website: user guides, reference configurations pages, FAQ & utilities * Investigate the possibility of versionning the new wiki pages with the code repository - Mailing lists * Copy the missing members of '[News]' from '[Nemo]' * Begin to use '[News]' & '[Systeam]' and keep '[Nemo]' & '[Nemo_st]' for external requests. 3) Critical switch of NEMO Users to the new architecture (1~2 whole days for operation) - Website (offline during the process) * Block registration of a new user and turn off the synchronization of the accounts to IPSL Forge * Private areas will be only accessible to ST, user connection will not open access to more content than public site. * Edit accordingly the public pages regarding the new architecture - IPSL Forge (online): remove access of the website accounts - IPSL Trac: review default permissions for basic user (merge 'developer' & 'authenticated' role) - Users Forge (online after website maintenance): * Recover the up-to-date accounts database from website * Open access to previous members from website with the same ID (login/passwd) - Mailing lists * Close '[Nemo]', '[Nemo_st]' & '[nemo_ticket]'. * De facto '[News]' & '[Systeam]' will become the ones to use. 4) Get ready for the EOL of website server (target Q1 2017) With the previous work done which will reduced the dependency with the other components (less content to manage and no external constraint), We can choose freely between 2 solutions: - simply copy the current website on a new server (easiest) - completely revise the website with a more user-friendly SCM and a pleasant design (needed)
  • description changed from
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), I propose its evolution. The main strategy is to reach a compromise between different groups with specific needs and integrated tools. A predetermined rule of one tool for one group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static No more registration for users nor dynamical content to prepare its relocation - Users -> New Forge for Users (repository + SCM) * Standalone authentication system * Own bug tracking system * New wiki - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, poll, personal page, private wiki, ...). Together a transfer of the mailing lists '[Nemo]' & '[Nemo_st]' from our local IT infrastructure to the hosted service 'Universalistes' by RENATER. It is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address 'news@nemo-ocean.eu' and no prefix (identified later by '[News]' ) -> Open access but no posting allowed expect from owners i.e. ST via NEMO Officers. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" 'systeam@nemo-ocean.eu' " "" "" ( "" " "" '[Systeam]') -> Subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket. It will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation.
    to
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE) consisting of: - a website (nemo-ocean.eu) which serves as a public portal - a Forge (forge.ipsl.jussieu.fr/nemo) composed of a SVN repository and a web project management software Trac - 2 mailing lists '[Nemo]' & '[Nemo_st]' respectively for the users and the developers community In anticipation of the end of life of the server hosting the website (planned for Q1 2017), I propose a global evolution which will impact all components but will also remove most of the existing flaws and fill several lacks: - Decentralize the IT system to improve its availability and security - Reduce the duplication and the scattering of the content, and facilitate its edition - Limit the needs for support or specific development, and simplify the administration tasks To be honest, this will give a little more work day by day to the NEMO Officers which must be balanced with more autonomy. The main strategy is to reach a compromise between different groups with specific needs and integrated tools. A predetermined rule of one tool for one group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static No more registration for users nor dynamical content to prepare its relocation/substitution - Users -> New Forge for Users (repository + SCM) * Standalone authentication system (a copy of the existing user accounts is considered) * Own bug tracking system * New wiki - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, poll, personal page, private wiki, ...). Together a transfer of the present mailing lists from our local IT infrastructure to the hosted service 'Universalistes' by RENATER is planned. It is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address 'news@nemo-ocean.eu' and no prefix (identified later by '[News]' ) -> Open access but no posting allowed expect from owners i.e. ST via NEMO Officers. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" 'systeam@nemo-ocean.eu' " "" "" ( "" " "" '[Systeam]') -> Subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket. It will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation.

Changed on 2016-03-14T17:35:22+01:00 by nicolasmartin:

Changed on 2016-03-14T17:35:22+01:00 by nicolasmartin:

  • implementation changed from
    This evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last. The schedule is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Independent operations on components with no external interference (few weeks) - Website (no particular operation scheduled) * Users still allowed to register and get access to the IPSL Forge (repository and Trac) * ST new collaborative work move to IPSL Trac (agenda, reports, document design & sharing, wikis, ...) - IPSL Trac * NEMO officers appointed as permissions administrator in order to manage their own developers within their institute * Complete by an internal script the Trac profiles from the informations of their IPSL Forge account (name & email) * Replace the global notification for '[Nemo_st]' (wiki and ticket updates) by a customizable system with 2 plugins # Allow the subscription for an email notification of wiki page updates. Sender: 'Trac Wiki Notification <nemo@forge.ipsl.jussieu.fr>' # Ticket creation & resolution notified to all i.e ST Others modifications notified only to the reporter, the owner and the 'Cc'ers of the ticket Sender: 'Trac Ticket Notification <nemo@forge.ipsl.jussieu.fr>' - IPSL Forge: NEMO officers appointed as project administrators in order to manage their own developers within their institute - IPSL repository: replace the global notification sending (commits) to '[Nemo_st]' by an internal script which will update the local mailing list every 30 mns from developers group. Sender: 'SVN Commit Notification <nemo@forge.ipsl.jussieu.fr>' - Mailing lists * Create a CRU ("Compte Réseau Universel") account for each NEMO Officer to access the RENATER network * "" '[News]' & '[Systeam]' on 'Universalistes' with Officers as owners 2) Users Forge (2 to 3 months) - Website: enable for a new user the subscription to '[News]' in addition of '[Nemo]' - Users Forge (offline or hidden) * Initialise the new repository and the replication by cron through ssh from IPSL repository, then monitor the synchronization * Configure the new SCM * Transfer and update user content from the website: user guides, configurations pages, FAQ & utilities * Investigate the possibility of versionning the new wiki pages with IPSL repository - Mailing lists * Copy the missing members of '[News]' from '[Nemo]' * Begin to use '[News]' & '[Systeam]' and keep '[Nemo]' & '[Nemo_st]' for external requests. 3) Critical switch to the new architecture (up to 6 months) - Website (probably offline for 1 day) * Block registration of a new user and turn off the synchronization of the accounts to IPSL Forge * Private areas will be only accessible to ST, user connection will be rejected * Edit accordingly the public pages regarding the new architecture - IPSL Forge (online): remove user access - IPSL Trac: review default permissions and groups with the removal of users - Users Forge (online after website maintenance): * Recover the up-to-date accounts database from website * Open access to previous members from website with the same ID (login/passwd) - Mailing lists * Close '[Nemo]', '[Nemo_st]' & '[nemo_ticket]'. * De facto '[News]' & '[Systeam]' will become the ones to use.
    to
    This evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last. The schedule is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Independent operations on components with no external interference (few weeks) - Website (no particular operation scheduled) * Users still allowed to register and get access to the IPSL Forge (repository and Trac) * New collaborative ST work move to IPSL Trac (agenda, reports, document design & sharing, wikis, ...) - IPSL Trac * NEMO officers appointed as permissions administrator in order to manage their own developers within their institute * Complete by an internal script the Trac profiles from the informations of their IPSL Forge account (name & email) * Replace the global notification for '[Nemo_st]' (wiki and ticket updates) by a customizable system with 2 plugins # Allow the subscription for an email notification of wiki page updates. Sender: 'Trac Wiki Notification <nemo@forge.ipsl.jussieu.fr>', Prefix: '[Wiki]' # Ticket creation & resolution notified to all i.e ST Others modifications notified only to the reporter, the owner and the 'Cc'ers of the ticket Sender: 'Trac Ticket Notification <nemo@forge.ipsl.jussieu.fr>', Prefix: '[Ticket]' - IPSL Forge: NEMO officers appointed as project administrators in order to manage their own developers within their institute - IPSL repository: replace the global notification sending (commits) to '[Nemo_st]' by an internal script which will update the local mailing list every 30 mns from developers group. Sender: 'SVN Commit Notification <nemo@forge.ipsl.jussieu.fr>', Prefix: '[Commit]' - Mailing lists * Create a CRU ("Compte Réseau Universel") account for each NEMO Officer to access the RENATER network * "" '[News]' & '[Systeam]' on 'Universalistes' with Officers as owners 2) Establishment of the Users Forge (2 to 3 months) - Website: enable for a new user the subscription to '[News]' in addition of '[Nemo]' - Users Forge (offline or hidden) * Initialise the new repository and the replication from IPSL repository, then monitor the synchronization * Configure the new SCM (bug tracking system, forum, wiki, ...) * Transfer and update user content from the website: user guides, reference configurations pages, FAQ & utilities * Investigate the possibility of versionning the new wiki pages with the code repository - Mailing lists * Copy the missing members of '[News]' from '[Nemo]' * Begin to use '[News]' & '[Systeam]' and keep '[Nemo]' & '[Nemo_st]' for external requests. 3) Critical switch of NEMO Users to the new architecture (1~2 whole days for operation) - Website (offline during the process) * Block registration of a new user and turn off the synchronization of the accounts to IPSL Forge * Private areas will be only accessible to ST, user connection will not open access to more content than public site. * Edit accordingly the public pages regarding the new architecture - IPSL Forge (online): remove access of the website accounts - IPSL Trac: review default permissions for basic user (merge 'developer' & 'authenticated' role) - Users Forge (online after website maintenance): * Recover the up-to-date accounts database from website * Open access to previous members from website with the same ID (login/passwd) - Mailing lists * Close '[Nemo]', '[Nemo_st]' & '[nemo_ticket]'. * De facto '[News]' & '[Systeam]' will become the ones to use. 4) Get ready for the EOL of website server (target Q1 2017) With the previous work done which will reduced the dependency with the other components (less content to manage and no external constraint), We can choose freely between 2 solutions: - simply copy the current website on a new server (easiest) - completely revise the website with a more user-friendly SCM and a pleasant design (needed)
  • description changed from
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), I propose its evolution. The main strategy is to reach a compromise between different groups with specific needs and integrated tools. A predetermined rule of one tool for one group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static No more registration for users nor dynamical content to prepare its relocation - Users -> New Forge for Users (repository + SCM) * Standalone authentication system * Own bug tracking system and wiki - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, poll, personal page, private wiki, ...). Together a transfer of the mailing lists '[Nemo]' & '[Nemo_st]' from our local IT infrastructure to the hosted service 'Universalistes' by RENATER. It is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address 'news@nemo-ocean.eu' and no prefix (identified later by '[News]' ) -> Open access but no posting allowed expect from owners i.e. ST via NEMO Officers. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" 'systeam@nemo-ocean.eu' " "" "" ( "" " "" '[Systeam]') -> Subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket. It will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation.
    to
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), I propose its evolution. The main strategy is to reach a compromise between different groups with specific needs and integrated tools. A predetermined rule of one tool for one group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static No more registration for users nor dynamical content to prepare its relocation - Users -> New Forge for Users (repository + SCM) * Standalone authentication system * Own bug tracking system * New wiki - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, poll, personal page, private wiki, ...). Together a transfer of the mailing lists '[Nemo]' & '[Nemo_st]' from our local IT infrastructure to the hosted service 'Universalistes' by RENATER. It is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address 'news@nemo-ocean.eu' and no prefix (identified later by '[News]' ) -> Open access but no posting allowed expect from owners i.e. ST via NEMO Officers. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" 'systeam@nemo-ocean.eu' " "" "" ( "" " "" '[Systeam]') -> Subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket. It will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation.

Changed on 2016-03-11T19:46:41+01:00 by nicolasmartin:

Changed on 2016-03-11T19:46:41+01:00 by nicolasmartin:

  • implementation changed from
    This evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last i.e. the switch of the source code access for the users from the official website to their new Forge. It is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Short term (few weeks): independent operations on components with no external interference - Website (no particular operation scheduled) * Users still allowed to register and get access to the IPSL Forge (repository and Trac) * ST new collaborative work move to IPSL Trac (agenda, reports, document design & sharing, wikis, ...) - IPSL Trac * NEMO officers appointed as permissions administrator in order to manage their own developers within their institute * Complete by an internal script the Trac profiles from the informations of their IPSL Forge account (name & email) * Switch the global notification for '[Nemo_st]' (wiki and ticket updates) to a custom system with 2 plugins # Allow the subscription for an email notification of wiki page updates. Sender: 'Trac Wiki Notification <nemo@forge.ipsl.jussieu.fr>' # Ticket creation & resolution notified to all i.e ST, others modifications notified only to the reporter, the owner and the 'Cc'ers of the ticket. Sender: 'Trac Ticket Notification <nemo@forge.ipsl.jussieu.fr>' - IPSL Forge: NEMO officers appointed as administrators for the project in order to manage their own developers within their institute - IPSL repository: switch the global notification sending (commits) from '[Nemo_st]' to an internal script which will update the local mailing list every 30 mns from developers group. Sender: 'SVN Commit Notification <nemo@forge.ipsl.jussieu.fr>' - Mailing lists * Create a CRU ("Compte Réseau Universel") account for each NEMO Officer to access the RENATER network * "" '[News]' & '[Systeam]' on 'Universalistes' with Officers as owners 2) Mid-term (1 to 3 months) - Users Forge (offline or hidden) * Initialise the new repository and the replication by cron through ssh from IPSL repository, then monitor the synchronisation * Configure the new SCM * Transfer and update wiki pages from the website: user guides, configurations pages, FAQ & utilities * Investigate the possibility of versionning the new wiki pages with IPSL repository - Mailing lists * Begin to use '[News]' & '[Systeam]' and keep '[Nemo]' & '[Nemo_st]' for external requests. 3) Long-term (up to 6 months) - Website * - IPSL Forge - Users Forge - Mailing lists * Close '[Nemo]', '[Nemo_st]' & '[nemo_ticket]'. * De facto '[News]' & '[Systeam]' will become the ones to use.
    to
    This evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last. The schedule is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Independent operations on components with no external interference (few weeks) - Website (no particular operation scheduled) * Users still allowed to register and get access to the IPSL Forge (repository and Trac) * ST new collaborative work move to IPSL Trac (agenda, reports, document design & sharing, wikis, ...) - IPSL Trac * NEMO officers appointed as permissions administrator in order to manage their own developers within their institute * Complete by an internal script the Trac profiles from the informations of their IPSL Forge account (name & email) * Replace the global notification for '[Nemo_st]' (wiki and ticket updates) by a customizable system with 2 plugins # Allow the subscription for an email notification of wiki page updates. Sender: 'Trac Wiki Notification <nemo@forge.ipsl.jussieu.fr>' # Ticket creation & resolution notified to all i.e ST Others modifications notified only to the reporter, the owner and the 'Cc'ers of the ticket Sender: 'Trac Ticket Notification <nemo@forge.ipsl.jussieu.fr>' - IPSL Forge: NEMO officers appointed as project administrators in order to manage their own developers within their institute - IPSL repository: replace the global notification sending (commits) to '[Nemo_st]' by an internal script which will update the local mailing list every 30 mns from developers group. Sender: 'SVN Commit Notification <nemo@forge.ipsl.jussieu.fr>' - Mailing lists * Create a CRU ("Compte Réseau Universel") account for each NEMO Officer to access the RENATER network * "" '[News]' & '[Systeam]' on 'Universalistes' with Officers as owners 2) Users Forge (2 to 3 months) - Website: enable for a new user the subscription to '[News]' in addition of '[Nemo]' - Users Forge (offline or hidden) * Initialise the new repository and the replication by cron through ssh from IPSL repository, then monitor the synchronization * Configure the new SCM * Transfer and update user content from the website: user guides, configurations pages, FAQ & utilities * Investigate the possibility of versionning the new wiki pages with IPSL repository - Mailing lists * Copy the missing members of '[News]' from '[Nemo]' * Begin to use '[News]' & '[Systeam]' and keep '[Nemo]' & '[Nemo_st]' for external requests. 3) Critical switch to the new architecture (up to 6 months) - Website (probably offline for 1 day) * Block registration of a new user and turn off the synchronization of the accounts to IPSL Forge * Private areas will be only accessible to ST, user connection will be rejected * Edit accordingly the public pages regarding the new architecture - IPSL Forge (online): remove user access - IPSL Trac: review default permissions and groups with the removal of users - Users Forge (online after website maintenance): * Recover the up-to-date accounts database from website * Open access to previous members from website with the same ID (login/passwd) - Mailing lists * Close '[Nemo]', '[Nemo_st]' & '[nemo_ticket]'. * De facto '[News]' & '[Systeam]' will become the ones to use.
  • description changed from
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), I propose its evolution in order to: - Clarify the roles with their policies and restricted areas - Ensure the availability, the scalability and the security - Limit the needs for development or support (costs reduction) - Reduce the duplication and the scattering of the content - Simplify the editing and administration tasks The main strategy is to reach a compromise between different groups with specific needs and integrated tools. A predetermined rule of one tool for one group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static, no more registration for users nor dynamical content to prepare its relocation. - Users -> New Forge for Users (repository + SCM) with its standalone authentication system and its own bug tracking system. - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, poll, personal page, private wiki, ...). Together a transfer of the mailing lists '[Nemo]' & '[Nemo_st]', from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (French national network for education and research), is an opportunity to redefine their object and change their configuration: - 'nemo@locean-ipsl.upmc.fr' mailing list (identified later by its prefix '[Nemo]' ) will become a stringent newsletter with a custom address 'news@nemo-ocean.eu' and no prefix (identified later by '[News]' ): open access but no posting allowed expect from owners i.e. ST via NEMO Officers. - 'nemo_st@locean-ipsl.upmc.fr' " " "" ( "" " " "" " "" '[Nemo_st]') "" "" " confidential list "" " hidden "" "" 'systeam@nemo-ocean.eu' and no prefix (identified later by '[Systeam]'): subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket, it will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation.
    to
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), I propose its evolution. The main strategy is to reach a compromise between different groups with specific needs and integrated tools. A predetermined rule of one tool for one group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static No more registration for users nor dynamical content to prepare its relocation - Users -> New Forge for Users (repository + SCM) * Standalone authentication system * Own bug tracking system and wiki - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, poll, personal page, private wiki, ...). Together a transfer of the mailing lists '[Nemo]' & '[Nemo_st]' from our local IT infrastructure to the hosted service 'Universalistes' by RENATER. It is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address 'news@nemo-ocean.eu' and no prefix (identified later by '[News]' ) -> Open access but no posting allowed expect from owners i.e. ST via NEMO Officers. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" 'systeam@nemo-ocean.eu' " "" "" ( "" " "" '[Systeam]') -> Subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket. It will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation.

Changed on 2016-03-11T18:35:39+01:00 by nicolasmartin:

Changed on 2016-03-11T18:35:39+01:00 by nicolasmartin:

  • implementation changed from
    This evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last i.e. the switch of the source code access for the users from the official website to their new Forge. It is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Short term (few weeks): independent operations on components with no external interference - Website: no particular operation schedule * Users still allowed to register and get access to the IPSL Forge (repository and Trac) * ST new collaborative work move to IPSL Trac (agenda, reports, sharing documents, wikis, ...) - IPSL Trac * NEMO officers appointed as permissions administrator in order to manage their own developers within their institute * Complete by an internal script the Trac profiles from the informations of their IPSL Forge account (name & email) * Switch the global notification for '[Nemo_st]' (wiki and ticket updates) to a custom system with 2 plugins # Allow the subscription for an email notification of wiki page updates. Sender: 'Trac Wiki Notification <nemo@forge.ipsl.jussieu.fr>' # Ticket creation & resolution notified to all i.e ST, others modifications notified only to the reporter, the owner and the 'Cc'ers of the ticket. Sender: 'Trac Ticket Notification <nemo@forge.ipsl.jussieu.fr>' - IPSL Forge * NEMO officers appointed as administrators for the project in order to manage their own developers within their institute - IPSL repository * Switch the global notification sending (commits) from '[Nemo_st]' to an internal script which will update the local mailing list every 30 mns from developers group. Sender: 'SVN Commit Notification <nemo@forge.ipsl.jussieu.fr>' - Mailing lists * Create a CRU ("Compte Réseau Universel") account for each NEMO Officer to access the RENATER network * "" '[News]' & '[Systeam]' on 'Universalistes' with Officers as owners 2) Mid-term (1 to 3 months) - Users Forge (offline or hidden) * Initialise the new repository and the replication by cron through ssh from IPSL repository, then monitor the synchronisation * Configure the new SCM * Transfer and update wiki pages from the website: user guides, configurations pages, FAQ & utilities * Investigate the possibility of versionning the new wiki pages with IPSL repository - Mailing lists * Begin to use '[News]' & '[Systeam]' and keep '[Nemo]' & '[Nemo_st]' for external requests. 3) Long-term (up to 6 months) - Website - IPSL Forge - Users Forge - Mailing lists * Close '[Nemo]', '[Nemo_st]' & '[nemo_ticket]'. * De facto '[News]' & '[Systeam]' will become the ones to use.
    to
    This evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last i.e. the switch of the source code access for the users from the official website to their new Forge. It is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Short term (few weeks): independent operations on components with no external interference - Website (no particular operation scheduled) * Users still allowed to register and get access to the IPSL Forge (repository and Trac) * ST new collaborative work move to IPSL Trac (agenda, reports, document design & sharing, wikis, ...) - IPSL Trac * NEMO officers appointed as permissions administrator in order to manage their own developers within their institute * Complete by an internal script the Trac profiles from the informations of their IPSL Forge account (name & email) * Switch the global notification for '[Nemo_st]' (wiki and ticket updates) to a custom system with 2 plugins # Allow the subscription for an email notification of wiki page updates. Sender: 'Trac Wiki Notification <nemo@forge.ipsl.jussieu.fr>' # Ticket creation & resolution notified to all i.e ST, others modifications notified only to the reporter, the owner and the 'Cc'ers of the ticket. Sender: 'Trac Ticket Notification <nemo@forge.ipsl.jussieu.fr>' - IPSL Forge: NEMO officers appointed as administrators for the project in order to manage their own developers within their institute - IPSL repository: switch the global notification sending (commits) from '[Nemo_st]' to an internal script which will update the local mailing list every 30 mns from developers group. Sender: 'SVN Commit Notification <nemo@forge.ipsl.jussieu.fr>' - Mailing lists * Create a CRU ("Compte Réseau Universel") account for each NEMO Officer to access the RENATER network * "" '[News]' & '[Systeam]' on 'Universalistes' with Officers as owners 2) Mid-term (1 to 3 months) - Users Forge (offline or hidden) * Initialise the new repository and the replication by cron through ssh from IPSL repository, then monitor the synchronisation * Configure the new SCM * Transfer and update wiki pages from the website: user guides, configurations pages, FAQ & utilities * Investigate the possibility of versionning the new wiki pages with IPSL repository - Mailing lists * Begin to use '[News]' & '[Systeam]' and keep '[Nemo]' & '[Nemo_st]' for external requests. 3) Long-term (up to 6 months) - Website * - IPSL Forge - Users Forge - Mailing lists * Close '[Nemo]', '[Nemo_st]' & '[nemo_ticket]'. * De facto '[News]' & '[Systeam]' will become the ones to use.
  • description changed from
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), I propose its evolution in order to: - Clarify the roles with their policies and restricted areas - Ensure the availability, the scalability and the security - Limit the needs for development or support (costs reduction) - Reduce the duplication and the scattering of the content - Simplify the editing and administration tasks The main strategy is to reach a compromise between different groups with specific needs and integrated tools. A predetermined rule of one tool for one group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static, no more registration for users nor dynamical content to prepare its relocation. - Users -> New Forge for Users (repository + SCM) with its standalone authentication system and its own bug tracking system. - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, poll, personal page, private wiki, ...). Together a transfer of the mailing lists '[Nemo]' & '[Nemo_st]', from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (French national network for education and research), is an opportunity to redefine their object and change their configuration: - 'nemo@locean-ipsl.upmc.fr' mailing list (identified later by its prefix '[Nemo]' ) will become a stringent newsletter with a custom address 'news@nemo-ocean.eu' and no prefix (identified later by '[News]' ): open access but no posting allowed expect from owners i.e. ST via NEMO Officers. - 'nemo_st@locean-ipsl.upmc.fr' " " "" ( "" " " "" " "" '[Nemo_st]') "" "" " confidential list "" " hidden "" "" 'systeam@nemo-ocean.eu' and no prefix (identified later by '[Systeam]'): subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket, it will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation.
    to
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), I propose its evolution in order to: - Clarify the roles with their policies and restricted areas - Ensure the availability, the scalability and the security - Limit the needs for development or support (costs reduction) - Reduce the duplication and the scattering of the content - Simplify the editing and administration tasks The main strategy is to reach a compromise between different groups with specific needs and integrated tools. A predetermined rule of one tool for one group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static, no more registration for users nor dynamical content to prepare its relocation. - Users -> New Forge for Users (repository + SCM) with its standalone authentication system and its own bug tracking system. - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, poll, personal page, private wiki, ...). Together a transfer of the mailing lists '[Nemo]' & '[Nemo_st]', from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (French national network for education and research), is an opportunity to redefine their object and change their configuration: - 'nemo@locean-ipsl.upmc.fr' mailing list (identified later by its prefix '[Nemo]' ) will become a stringent newsletter with a custom address 'news@nemo-ocean.eu' and no prefix (identified later by '[News]' ): open access but no posting allowed expect from owners i.e. ST via NEMO Officers. - 'nemo_st@locean-ipsl.upmc.fr' " " "" ( "" " " "" " "" '[Nemo_st]') "" "" " confidential list "" " hidden "" "" 'systeam@nemo-ocean.eu' and no prefix (identified later by '[Systeam]'): subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket, it will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation.

Changed on 2016-03-11T17:43:49+01:00 by nicolasmartin:

Changed on 2016-03-11T17:43:49+01:00 by nicolasmartin:

  • implementation changed from
    This evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last i.e. the switch of the source code access for the users from the official website to their new Forge. It is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Short term (few weeks): independent operations on components with no external interference - Website: no particular operation * Users still allowed to register and get access to the IPSL Forge (repository and Trac) * ST - IPSL Trac : * NEMO officers appointed as permissions administrator in order to manage their own developers within their institute * Complete by an internal script the Trac profiles from the informations of their IPSL Forge account (name & email) * Switch the global notification for '[Nemo_st]' (wiki and ticket updates) to a custom system with 2 plugins # Allow the subscription for an email notification of wiki page updates. Sender: 'Trac Wiki Notification <nemo@forge.ipsl.jussieu.fr>' # Ticket creation & resolution notified to all i.e ST, others modifications notified only to the reporter, the owner and the 'Cc'ers of the ticket. Sender: 'Trac Ticket Notification <nemo@forge.ipsl.jussieu.fr>' - IPSL Forge * NEMO officers appointed as administrators for the project in order to manage their own developers within their institute - IPSL repository * Switch the global notification sending (commits) from '[Nemo_st]' to an internal script which will update the local mailing list every 30 mns from developers group. Sender: 'SVN Commit Notification <nemo@forge.ipsl.jussieu.fr>' - Mailing lists * Create a CRU ("Compte Réseau Universel") account for each NEMO Officer to access the RENATER network * "" '[News]' & '[Systeam]' on 'Universalistes' with Officers as owners 2) Mid-term (1 to 3 months) - Users Forge * Initialise the new repository and the replication by cron through ssh from IPSL repository, then monitor the synchronisation * Configuration new SCM * Transfer and update wiki pages from the website: user guides, configurations pages, FAQ & utilities * Investigate the possibility of versionning the new wiki pages with IPSL repository - Mailing lists * Begin to use '[News]' & '[Systeam]' and keep '[Nemo]' & '[Nemo_st]' for external requests. 3) Long-term (up to 6 months) - Website - IPSL Forge - Users Forge - Mailing lists * /Close '[nemo_ticket]' mailing list /?
    to
    This evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last i.e. the switch of the source code access for the users from the official website to their new Forge. It is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Short term (few weeks): independent operations on components with no external interference - Website: no particular operation schedule * Users still allowed to register and get access to the IPSL Forge (repository and Trac) * ST new collaborative work move to IPSL Trac (agenda, reports, sharing documents, wikis, ...) - IPSL Trac * NEMO officers appointed as permissions administrator in order to manage their own developers within their institute * Complete by an internal script the Trac profiles from the informations of their IPSL Forge account (name & email) * Switch the global notification for '[Nemo_st]' (wiki and ticket updates) to a custom system with 2 plugins # Allow the subscription for an email notification of wiki page updates. Sender: 'Trac Wiki Notification <nemo@forge.ipsl.jussieu.fr>' # Ticket creation & resolution notified to all i.e ST, others modifications notified only to the reporter, the owner and the 'Cc'ers of the ticket. Sender: 'Trac Ticket Notification <nemo@forge.ipsl.jussieu.fr>' - IPSL Forge * NEMO officers appointed as administrators for the project in order to manage their own developers within their institute - IPSL repository * Switch the global notification sending (commits) from '[Nemo_st]' to an internal script which will update the local mailing list every 30 mns from developers group. Sender: 'SVN Commit Notification <nemo@forge.ipsl.jussieu.fr>' - Mailing lists * Create a CRU ("Compte Réseau Universel") account for each NEMO Officer to access the RENATER network * "" '[News]' & '[Systeam]' on 'Universalistes' with Officers as owners 2) Mid-term (1 to 3 months) - Users Forge (offline or hidden) * Initialise the new repository and the replication by cron through ssh from IPSL repository, then monitor the synchronisation * Configure the new SCM * Transfer and update wiki pages from the website: user guides, configurations pages, FAQ & utilities * Investigate the possibility of versionning the new wiki pages with IPSL repository - Mailing lists * Begin to use '[News]' & '[Systeam]' and keep '[Nemo]' & '[Nemo_st]' for external requests. 3) Long-term (up to 6 months) - Website - IPSL Forge - Users Forge - Mailing lists * Close '[Nemo]', '[Nemo_st]' & '[nemo_ticket]'. * De facto '[News]' & '[Systeam]' will become the ones to use.

Changed on 2016-03-11T17:06:07+01:00 by nicolasmartin:

Changed on 2016-03-11T17:06:07+01:00 by nicolasmartin:

  • implementation changed from
    This evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last i.e. the switch of the source code access for the users from the official website to their new Forge. It is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Short term (few weeks): independent operations on components with no external interference - Website - Trac : * NEMO officers appointed as permissions administrator in order to manage their own developers within their institute * Complete by an internal script the Trac profiles from the informations of their IPSL Forge account (name & email) * Switch the global notification for '[Nemo_st]' (wiki and ticket updates) to a custom system with 2 plugins # Allow the subscription for an email notification of wiki page updates. Sender: 'Trac Wiki Notification <nemo@forge.ipsl.jussieu.fr>' # Ticket creation & resolution notified to all i.e ST, others modifications notified only to the reporter, the owner and the 'Cc'ers of the ticket. Sender: 'Trac Ticket Notification <nemo@forge.ipsl.jussieu.fr>' - IPSL Forge * NEMO officers appointed as administrators for the project in order to manage their own developers within their institute * Switch the global notification sending (commits) from '[Nemo_st]' to an internal script which will update the local mailing list every 30 mns from developers group. Sender: 'SVN Commit Notification <nemo@forge.ipsl.jussieu.fr>' - Mailing lists * Create a CRU ("Compte Réseau Universel") account for each NEMO Officer to access the RENATER network * "" '[News]' & '[Systeam]' on 'Universalistes' with Officers as owners 2) Mid-term (1 to 3 months) - Users Forge * - Mailing lists * Once we have reduced the unwanted posts on '[Nemo_st]' (Forge mainly), begin to use '[Systeam]' and keep '[Nemo_st]' for external requests. 3) Long-term (up to 6 months) - Website - IPSL Forge - Users Forge - Mailing lists * /Close '[nemo_ticket]' mailing list /?
    to
    This evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last i.e. the switch of the source code access for the users from the official website to their new Forge. It is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Short term (few weeks): independent operations on components with no external interference - Website: no particular operation * Users still allowed to register and get access to the IPSL Forge (repository and Trac) * ST - IPSL Trac : * NEMO officers appointed as permissions administrator in order to manage their own developers within their institute * Complete by an internal script the Trac profiles from the informations of their IPSL Forge account (name & email) * Switch the global notification for '[Nemo_st]' (wiki and ticket updates) to a custom system with 2 plugins # Allow the subscription for an email notification of wiki page updates. Sender: 'Trac Wiki Notification <nemo@forge.ipsl.jussieu.fr>' # Ticket creation & resolution notified to all i.e ST, others modifications notified only to the reporter, the owner and the 'Cc'ers of the ticket. Sender: 'Trac Ticket Notification <nemo@forge.ipsl.jussieu.fr>' - IPSL Forge * NEMO officers appointed as administrators for the project in order to manage their own developers within their institute - IPSL repository * Switch the global notification sending (commits) from '[Nemo_st]' to an internal script which will update the local mailing list every 30 mns from developers group. Sender: 'SVN Commit Notification <nemo@forge.ipsl.jussieu.fr>' - Mailing lists * Create a CRU ("Compte Réseau Universel") account for each NEMO Officer to access the RENATER network * "" '[News]' & '[Systeam]' on 'Universalistes' with Officers as owners 2) Mid-term (1 to 3 months) - Users Forge * Initialise the new repository and the replication by cron through ssh from IPSL repository, then monitor the synchronisation * Configuration new SCM * Transfer and update wiki pages from the website: user guides, configurations pages, FAQ & utilities * Investigate the possibility of versionning the new wiki pages with IPSL repository - Mailing lists * Begin to use '[News]' & '[Systeam]' and keep '[Nemo]' & '[Nemo_st]' for external requests. 3) Long-term (up to 6 months) - Website - IPSL Forge - Users Forge - Mailing lists * /Close '[nemo_ticket]' mailing list /?
  • description changed from
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), I propose its evolution in order to: - Clarify the roles with their policies and restricted areas - Ensure the availability, the scalability and the security - Limit the needs for development or support (costs reduction) - Reduce the duplication and the scattering of the content - Simplify the editing and administration tasks The main strategy is to reach a compromise between different groups with specific needs and integrated tools. A predetermined rule of one tool for one group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static, no more registration for users nor dynamical content to prepare its relocation. - Users -> New Forge for Users (repository + SCM) with its standalone authentication system and its own bug tracking system. - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, poll, private wiki, ...). Together a transfer of the mailing lists '[Nemo]' & '[Nemo_st]', from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (French national network for education and research), is an opportunity to redefine their object and change their configuration: - 'nemo@locean-ipsl.upmc.fr' mailing list (identified later by its prefix '[Nemo]' ) will become a stringent newsletter with a custom address 'news@nemo-ocean.eu' and no prefix (identified later by '[News]' ): open access but no posting allowed expect from owners i.e. ST via NEMO Officers. - 'nemo_st@locean-ipsl.upmc.fr' " " "" ( "" " " "" " "" '[Nemo_st]') "" "" " confidential list "" " hidden "" "" 'systeam@nemo-ocean.eu' and no prefix (identified later by '[Systeam]'): subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket, it will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation described below.
    to
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), I propose its evolution in order to: - Clarify the roles with their policies and restricted areas - Ensure the availability, the scalability and the security - Limit the needs for development or support (costs reduction) - Reduce the duplication and the scattering of the content - Simplify the editing and administration tasks The main strategy is to reach a compromise between different groups with specific needs and integrated tools. A predetermined rule of one tool for one group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static, no more registration for users nor dynamical content to prepare its relocation. - Users -> New Forge for Users (repository + SCM) with its standalone authentication system and its own bug tracking system. - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, poll, personal page, private wiki, ...). Together a transfer of the mailing lists '[Nemo]' & '[Nemo_st]', from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (French national network for education and research), is an opportunity to redefine their object and change their configuration: - 'nemo@locean-ipsl.upmc.fr' mailing list (identified later by its prefix '[Nemo]' ) will become a stringent newsletter with a custom address 'news@nemo-ocean.eu' and no prefix (identified later by '[News]' ): open access but no posting allowed expect from owners i.e. ST via NEMO Officers. - 'nemo_st@locean-ipsl.upmc.fr' " " "" ( "" " " "" " "" '[Nemo_st]') "" "" " confidential list "" " hidden "" "" 'systeam@nemo-ocean.eu' and no prefix (identified later by '[Systeam]'): subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket, it will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation.

Changed on 2016-03-10T20:57:24+01:00 by nicolasmartin:

Changed on 2016-03-10T20:57:24+01:00 by nicolasmartin:

  • implementation changed from
    This evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last i.e. the switch of the source code access for the users from the official website to their new Forge. It is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Short term (few weeks): independent operations on components with no external interference - Website - Trac : * NEMO officers appointed as permissions administrator in order to manage their own developers within their institute * Complete by an internal script the Trac profiles from the informations of their IPSL Forge account (name & email) * Switch the global notification for '[Nemo_st]' (wiki and ticket updates) to a custom system with 2 Trac plugins # Allow the subscription of an email notification for wiki page updates. Sender: 'Trac Wiki Notification <nemo@forge.ipsl.jussieu.fr>' # Ticket creation & resolution notified to all i.e ST, others modifications notified only to the reporter, the owner and the 'Cc'ers of the ticket. Sender: 'Trac Ticket Notification <nemo@forge.ipsl.jussieu.fr>' - IPSL Forge * NEMO officers appointed as administrators for the project in order to manage their own developers within their institute * Switch the global notification sending (commits) from '[Nemo_st]' to an internal script which will update the local mailing list every 30 mns from developers group. Sender: 'SVN Commit Notification <nemo@forge.ipsl.jussieu.fr>' - Mailing lists * Create a CRU ("Compte Réseau Universel") account for each NEMO Officer to access the RENATER network * "" '[News]' & '[Systeam]' on 'Universalistes' with Officers as owners 2) Mid-term (1 to 3 months) - Users Forge * - Mailing lists * Once we have reduced the unwanted posts on '[Nemo_st]' (Forge mainly), begin to use '[Systeam]' and keep '[Nemo_st]' for external requests. 3) Long-term (up to 6 months) - Website - IPSL Forge - Users Forge - Mailing lists * /Close '[nemo_ticket]' mailing list /?
    to
    This evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last i.e. the switch of the source code access for the users from the official website to their new Forge. It is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Short term (few weeks): independent operations on components with no external interference - Website - Trac : * NEMO officers appointed as permissions administrator in order to manage their own developers within their institute * Complete by an internal script the Trac profiles from the informations of their IPSL Forge account (name & email) * Switch the global notification for '[Nemo_st]' (wiki and ticket updates) to a custom system with 2 plugins # Allow the subscription for an email notification of wiki page updates. Sender: 'Trac Wiki Notification <nemo@forge.ipsl.jussieu.fr>' # Ticket creation & resolution notified to all i.e ST, others modifications notified only to the reporter, the owner and the 'Cc'ers of the ticket. Sender: 'Trac Ticket Notification <nemo@forge.ipsl.jussieu.fr>' - IPSL Forge * NEMO officers appointed as administrators for the project in order to manage their own developers within their institute * Switch the global notification sending (commits) from '[Nemo_st]' to an internal script which will update the local mailing list every 30 mns from developers group. Sender: 'SVN Commit Notification <nemo@forge.ipsl.jussieu.fr>' - Mailing lists * Create a CRU ("Compte Réseau Universel") account for each NEMO Officer to access the RENATER network * "" '[News]' & '[Systeam]' on 'Universalistes' with Officers as owners 2) Mid-term (1 to 3 months) - Users Forge * - Mailing lists * Once we have reduced the unwanted posts on '[Nemo_st]' (Forge mainly), begin to use '[Systeam]' and keep '[Nemo_st]' for external requests. 3) Long-term (up to 6 months) - Website - IPSL Forge - Users Forge - Mailing lists * /Close '[nemo_ticket]' mailing list /?

Changed on 2016-03-10T20:54:18+01:00 by nicolasmartin:

Changed on 2016-03-10T20:54:18+01:00 by nicolasmartin:

  • implementation changed from
    This evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last i.e. the switch of the source code access for the users from the official website to their new Forge. It is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Short term (few weeks): independent operations on CDE components with no external interference - Website - Trac : * NEMO officers appointed as permissions administrator in order to manage their own developers within their institute * Complete by an internal script the Trac profiles from the informations of their IPSL Forge account (name & email) * Switch the global notification sending (wiki and ticket updates) from '[Nemo_st]' mailing list to a custom one with 2 Trac plugins # Allow the subscription of email notifications for wiki page updates # Ticket creation & resolution notified to all i.e ST, others modifications notified only to the reporter, the owner and the 'Cc'ers of the ticket. - IPSL Forge * NEMO officers appointed as administrators for the project in order to manage their own developers within their institute * Switch the global notification sending (commits) from '[Nemo_st]' mailing list to an internal script which will update the developers mailing list every 30 mns. - Mailing lists * Create a CRU account for each NEMO Officers to access the RENATER network * "" the new mailing lists on 'Universalistes' with NEMO Officers as owners 2) Mid-term (1 to 3 months) - Mailing lists * Once '[Nemo_st]' has been 3) Long-term (up to 6 months) - Mailing lists * /Close '[nemo_ticket]' mailing list /?
    to
    This evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last i.e. the switch of the source code access for the users from the official website to their new Forge. It is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Short term (few weeks): independent operations on components with no external interference - Website - Trac : * NEMO officers appointed as permissions administrator in order to manage their own developers within their institute * Complete by an internal script the Trac profiles from the informations of their IPSL Forge account (name & email) * Switch the global notification for '[Nemo_st]' (wiki and ticket updates) to a custom system with 2 Trac plugins # Allow the subscription of an email notification for wiki page updates. Sender: 'Trac Wiki Notification <nemo@forge.ipsl.jussieu.fr>' # Ticket creation & resolution notified to all i.e ST, others modifications notified only to the reporter, the owner and the 'Cc'ers of the ticket. Sender: 'Trac Ticket Notification <nemo@forge.ipsl.jussieu.fr>' - IPSL Forge * NEMO officers appointed as administrators for the project in order to manage their own developers within their institute * Switch the global notification sending (commits) from '[Nemo_st]' to an internal script which will update the local mailing list every 30 mns from developers group. Sender: 'SVN Commit Notification <nemo@forge.ipsl.jussieu.fr>' - Mailing lists * Create a CRU ("Compte Réseau Universel") account for each NEMO Officer to access the RENATER network * "" '[News]' & '[Systeam]' on 'Universalistes' with Officers as owners 2) Mid-term (1 to 3 months) - Users Forge * - Mailing lists * Once we have reduced the unwanted posts on '[Nemo_st]' (Forge mainly), begin to use '[Systeam]' and keep '[Nemo_st]' for external requests. 3) Long-term (up to 6 months) - Website - IPSL Forge - Users Forge - Mailing lists * /Close '[nemo_ticket]' mailing list /?
  • description changed from
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), I propose its evolution in order to: - Clarify the roles with their policies and restricted areas - Ensure the availability, the scalability and the security - Limit the needs for development or support (costs reduction) - Reduce the duplication and the scattering of the content - Simplify the editing and administration tasks The main strategy is to reach a compromise between different groups with specific needs and integrated tools. A predetermined rule of one tool for one group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static, no more registration for users nor dynamical content to prepare its relocation. - Users -> New Forge for Users (repository + SCM) with its standalone authentication system and its own bug tracking system. - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, poll, private wiki, ...). Together a transfer of the mailing lists '[Nemo]' & '[Nemo_st]', from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (French national network for education and research), is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address ('newsletter@nemo-ocean.eu'): open access but no posting allowed expect from owners i.e. the System Team via NEMO Officers. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" ('systeam@nemo-ocean.eu') : subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket, it will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation described below.
    to
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), I propose its evolution in order to: - Clarify the roles with their policies and restricted areas - Ensure the availability, the scalability and the security - Limit the needs for development or support (costs reduction) - Reduce the duplication and the scattering of the content - Simplify the editing and administration tasks The main strategy is to reach a compromise between different groups with specific needs and integrated tools. A predetermined rule of one tool for one group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static, no more registration for users nor dynamical content to prepare its relocation. - Users -> New Forge for Users (repository + SCM) with its standalone authentication system and its own bug tracking system. - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, poll, private wiki, ...). Together a transfer of the mailing lists '[Nemo]' & '[Nemo_st]', from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (French national network for education and research), is an opportunity to redefine their object and change their configuration: - 'nemo@locean-ipsl.upmc.fr' mailing list (identified later by its prefix '[Nemo]' ) will become a stringent newsletter with a custom address 'news@nemo-ocean.eu' and no prefix (identified later by '[News]' ): open access but no posting allowed expect from owners i.e. ST via NEMO Officers. - 'nemo_st@locean-ipsl.upmc.fr' " " "" ( "" " " "" " "" '[Nemo_st]') "" "" " confidential list "" " hidden "" "" 'systeam@nemo-ocean.eu' and no prefix (identified later by '[Systeam]'): subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket, it will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation described below.

Changed on 2016-03-10T19:09:37+01:00 by nicolasmartin:

Changed on 2016-03-10T19:09:37+01:00 by nicolasmartin:

  • implementation changed from
    This evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last i.e. the switch of the source code access for the users from the official website to their new Forge. It is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Short term: independent operations on CDE components with no external interference - Website - Trac NEMO officers granted as permissions administrator in order to manage their own developers within their institute Complete the Trac profiles from the informations of their IPSL Forge account (name & email) Switch the notification sending (wiki and ticket updates) from '[Nemo_st]' mailing list to - IPSL Forge NEMO officers granted as administrators for the project in order to manage their own developers within their institute Switch the notification sending (commits) from '[Nemo_st]' mailing list to - Mailing lists Create a CRU account for each NEMO Officers to access to the RENATER network "" the new mailing lists on 'Universalistes' with NEMO Officers as owners 2) Mid-term - Mailing lists NEMO officers granted as '[Nemo_st]' administrators 3) Long-term
    to
    This evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last i.e. the switch of the source code access for the users from the official website to their new Forge. It is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Short term (few weeks): independent operations on CDE components with no external interference - Website - Trac : * NEMO officers appointed as permissions administrator in order to manage their own developers within their institute * Complete by an internal script the Trac profiles from the informations of their IPSL Forge account (name & email) * Switch the global notification sending (wiki and ticket updates) from '[Nemo_st]' mailing list to a custom one with 2 Trac plugins # Allow the subscription of email notifications for wiki page updates # Ticket creation & resolution notified to all i.e ST, others modifications notified only to the reporter, the owner and the 'Cc'ers of the ticket. - IPSL Forge * NEMO officers appointed as administrators for the project in order to manage their own developers within their institute * Switch the global notification sending (commits) from '[Nemo_st]' mailing list to an internal script which will update the developers mailing list every 30 mns. - Mailing lists * Create a CRU account for each NEMO Officers to access the RENATER network * "" the new mailing lists on 'Universalistes' with NEMO Officers as owners 2) Mid-term (1 to 3 months) - Mailing lists * Once '[Nemo_st]' has been 3) Long-term (up to 6 months) - Mailing lists * /Close '[nemo_ticket]' mailing list /?

Changed on 2016-03-10T18:04:39+01:00 by nicolasmartin:

Changed on 2016-03-10T18:04:39+01:00 by nicolasmartin:

  • implementation changed from
    This evolution must be happen in steps, the critical part who will be probably done as a last is the transfer of the source code access for the users to their new Forge. - Website - Trac NEMO officers granted - IPSL Forge NEMO officers granted as administrators for the project - Mailing lists NEMO officers granted as '[Nemo_st]' administrators
    to
    This evolution must be happen in steps, from the simplest and the easiest actions to the most critical part who will be probably done as a last i.e. the switch of the source code access for the users from the official website to their new Forge. It is dictated by the interactions between all components of the NEMO CDE, both from a technical standpoint (communications between us) and a working standpoint (how we and the people use it). 1) Short term: independent operations on CDE components with no external interference - Website - Trac NEMO officers granted as permissions administrator in order to manage their own developers within their institute Complete the Trac profiles from the informations of their IPSL Forge account (name & email) Switch the notification sending (wiki and ticket updates) from '[Nemo_st]' mailing list to - IPSL Forge NEMO officers granted as administrators for the project in order to manage their own developers within their institute Switch the notification sending (commits) from '[Nemo_st]' mailing list to - Mailing lists Create a CRU account for each NEMO Officers to access to the RENATER network "" the new mailing lists on 'Universalistes' with NEMO Officers as owners 2) Mid-term - Mailing lists NEMO officers granted as '[Nemo_st]' administrators 3) Long-term
  • description changed from
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), I propose its evolution in order to: - Clarify the roles with their policies and restricted areas - Ensure the availability, the scalability and the security - Limit the needs for development or support (costs reduction) - Reduce the duplication and the scattering of the content - Simplify the editing and administration tasks The main strategy is to reach a compromise between different groups with specific needs and integrated tools. A predetermined rule of one tool for one group brings to the next scheme: - Public -> Current website restricted to its public content which is almost static, no more registration (except for editors) or dynamical content. - Users -> New Forge for Users (repository + SCM) with its standalone authentication system and its own bug tracking system. - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, discussion forum, forms, custom notifications, polls, private wikis, ...). Together a transfer of the mailing lists '[Nemo]' & '[Nemo_st]', from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (French national network for education and research), is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address ('newsletter@nemo-ocean.eu'): open access but no posting allowed expect from owners i.e. the System Team via NEMO Officers. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" ('systeam@nemo-ocean.eu'): subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge, it will ensure the moderation activities and the archiving for further search.
    to
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), I propose its evolution in order to: - Clarify the roles with their policies and restricted areas - Ensure the availability, the scalability and the security - Limit the needs for development or support (costs reduction) - Reduce the duplication and the scattering of the content - Simplify the editing and administration tasks The main strategy is to reach a compromise between different groups with specific needs and integrated tools. A predetermined rule of one tool for one group brings to the next scheme: - Public -> Current website will be restricted to its public content which is almost static, no more registration for users nor dynamical content to prepare its relocation. - Users -> New Forge for Users (repository + SCM) with its standalone authentication system and its own bug tracking system. - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, discussion forum, form, custom notification, poll, private wiki, ...). Together a transfer of the mailing lists '[Nemo]' & '[Nemo_st]', from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (French national network for education and research), is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address ('newsletter@nemo-ocean.eu'): open access but no posting allowed expect from owners i.e. the System Team via NEMO Officers. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" ('systeam@nemo-ocean.eu') : subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge by opening a forum discussion or a ticket, it will ensure the moderation activities and the archiving for further search. Obviously, this change will be gradual and a overlap phase between the previous mailing lists and the new ones should be happen during the implementation described below.

Changed on 2016-03-10T02:53:08+01:00 by nicolasmartin:

Changed on 2016-03-10T02:53:08+01:00 by nicolasmartin:

  • implementation changed from
    - Website - Trac NEMO officers granted - IPSL Forge NEMO officers granted as administrators for the project - Mailing lists NEMO officers granted as '[Nemo_st]' administrators
    to
    This evolution must be happen in steps, the critical part who will be probably done as a last is the transfer of the source code access for the users to their new Forge. - Website - Trac NEMO officers granted - IPSL Forge NEMO officers granted as administrators for the project - Mailing lists NEMO officers granted as '[Nemo_st]' administrators
  • description changed from
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), I propose its evolution in order to: - Clarify the roles with their policies and restricted areas - Ensure the availability, the scalability and the security - Limit the needs for development or support (costs reduction) - Reduce the duplication and the scattering of the content - Simplify the editing and administration tasks The main strategy is to reach a compromise between different groups with specific needs and integrated tools. It results - Public -> Website restricted to its public area, no more registration (except for editors) . - Users -> New Forge for Users (repository + SCM) with its standalone authentication system and own bug tracking system. - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access by granting an administrator per institute. - System Team/external Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, discussion forum, forms, notifications, polls, private wikis, ...). Together, a transfer of the mailing lists '[Nemo]' & '[Nemo_st]' from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (French national network for education and research) is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address ('newsletter@nemo-ocean.eu'): open access but no posting allowed. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" ('systeam@nemo-ocean.eu'): subscription controlled by NEMO Officers, no external posting. It means that any request (informations or support) will be only posted from the new Forge, it will ensure the moderation activities and the archiving for further search.
    to
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), I propose its evolution in order to: - Clarify the roles with their policies and restricted areas - Ensure the availability, the scalability and the security - Limit the needs for development or support (costs reduction) - Reduce the duplication and the scattering of the content - Simplify the editing and administration tasks The main strategy is to reach a compromise between different groups with specific needs and integrated tools. A predetermined rule of one tool for one group brings to the next scheme: - Public -> Current website restricted to its public content which is almost static, no more registration (except for editors) or dynamical content. - Users -> New Forge for Users (repository + SCM) with its standalone authentication system and its own bug tracking system. - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access by granting an administrator per institute (NEMO Officer). - System Team/external Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, discussion forum, forms, custom notifications, polls, private wikis, ...). Together a transfer of the mailing lists '[Nemo]' & '[Nemo_st]', from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (French national network for education and research), is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address ('newsletter@nemo-ocean.eu'): open access but no posting allowed expect from owners i.e. the System Team via NEMO Officers. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" ('systeam@nemo-ocean.eu'): subscription controlled by NEMO Officers, no external posting. In the future, it would mean that anyone who wants to get in touch with us will go through the new Forge, it will ensure the moderation activities and the archiving for further search.

Changed on 2016-03-10T01:56:35+01:00 by nicolasmartin:

Changed on 2016-03-10T01:56:35+01:00 by nicolasmartin:

  • description changed from
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), I propose its evolution in order to: - Clarify the roles with their policies and restricted areas - Ensure the availability, the scalability and the security - Limit the needs for development or support (costs reduction) - Reduce the duplication and the scattering of the content - Simplify the editing and administration tasks The main strategy is to reach a compromise between different groups with and few integrated tools. It results - Public -> Website restricted to its public area, no more registration (except for editors) . - Users -> New Forge for Users (repository + SCM) with its standalone authentication system and own bug tracking system. - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access by granting an administrator per institute. - System Team/external Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, discussion forum, forms, notifications, polls, private wikis, ...). Together, a transfer of the mailing lists '[Nemo]' & '[Nemo_st]' from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (French national network for education and research) is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address ('newsletter@nemo-ocean.eu'): open access but no posting allowed. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" ('systeam@nemo-ocean.eu'): subscription controlled by NEMO Officers, no external posting. It means that any request (informations or support) will be only posted from the new Forge, it will ensure the moderation activities and the archiving for further search.
    to
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), I propose its evolution in order to: - Clarify the roles with their policies and restricted areas - Ensure the availability, the scalability and the security - Limit the needs for development or support (costs reduction) - Reduce the duplication and the scattering of the content - Simplify the editing and administration tasks The main strategy is to reach a compromise between different groups with specific needs and integrated tools. It results - Public -> Website restricted to its public area, no more registration (except for editors) . - Users -> New Forge for Users (repository + SCM) with its standalone authentication system and own bug tracking system. - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access by granting an administrator per institute. - System Team/external Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, discussion forum, forms, notifications, polls, private wikis, ...). Together, a transfer of the mailing lists '[Nemo]' & '[Nemo_st]' from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (French national network for education and research) is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address ('newsletter@nemo-ocean.eu'): open access but no posting allowed. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" ('systeam@nemo-ocean.eu'): subscription controlled by NEMO Officers, no external posting. It means that any request (informations or support) will be only posted from the new Forge, it will ensure the moderation activities and the archiving for further search.

Changed on 2016-03-09T01:28:09+01:00 by nicolasmartin:

Changed on 2016-03-09T01:28:09+01:00 by nicolasmartin:

  • description changed from
    Since my introduction into the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), an evolution will be carried out in order to: - Clarify the roles with their policies and restricted areas - Ensure the availability, the scalability and the security - Limit the needs for development or support (costs reduction) - Reduce the duplication and fragmentation of the content - Simplify the edition and administration tasks The main strategy is to reach a compromise between groups (specific needs) and tools (aggregation and integration). It results - Public -> Website reduced to its public area, no more registration except for editors. - Users -> New Forge for Users (repository + SCM) with its standalone authentication system and own bug tracking system. - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access by granting an administrator per institute. - System Team/external Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, discussion forum, forms, notifications, polls, private wikis, ...). Together, a transfer of the mailing lists '[Nemo]' & '[Nemo_st]' from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (French national network for education and research) is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address ('newsletter@nemo-ocean.eu'): open access but no posting allowed. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" ('systeam@nemo-ocean.eu'): subscription controlled by NEMO Officers, no external posting. It means that any informations or support requests will be only posted from the new Forge, it will ensure the moderation activities and the archiving for further search.
    to
    Since I joined the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), I propose its evolution in order to: - Clarify the roles with their policies and restricted areas - Ensure the availability, the scalability and the security - Limit the needs for development or support (costs reduction) - Reduce the duplication and the scattering of the content - Simplify the editing and administration tasks The main strategy is to reach a compromise between different groups with and few integrated tools. It results - Public -> Website restricted to its public area, no more registration (except for editors) . - Users -> New Forge for Users (repository + SCM) with its standalone authentication system and own bug tracking system. - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access by granting an administrator per institute. - System Team/external Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, discussion forum, forms, notifications, polls, private wikis, ...). Together, a transfer of the mailing lists '[Nemo]' & '[Nemo_st]' from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (French national network for education and research) is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address ('newsletter@nemo-ocean.eu'): open access but no posting allowed. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" ('systeam@nemo-ocean.eu'): subscription controlled by NEMO Officers, no external posting. It means that any request (informations or support) will be only posted from the new Forge, it will ensure the moderation activities and the archiving for further search.

Changed on 2016-03-09T01:01:12+01:00 by nicolasmartin:

Changed on 2016-03-09T01:01:12+01:00 by nicolasmartin:

  • description changed from
    Since my introduction into the System Team, I lead for the year 2015 an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), an evolution will be carried out in order to: - Clarifying the roles, policies & areas - Ensuring the availability, the scalability and the security - Limiting needs for development or support (costs reduction) - Reducing the duplication and fragmentation of the content - Simplifying the edition and administration tasks The main strategy is to make a compromise between groups with specific needs / Tools aggregation and integration. It results - Public -> Website reduced to its public area, no more registration except for editors - Users -> New Forge for Users (repository + SCM) with its standalone authentication system and own bug tracking system. - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access - ST/Developers/Contributors/Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, private wikis, forms, discussion forum, ...) Together, a transfer of the mailing lists '[Nemo]' & '[Nemo_st]' from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (French national network for education and research) is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address ('newsletter@nemo-ocean.eu'): open access but no posting allowed. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" ('systeam@nemo-ocean.eu'): subscription controlled by NEMO Officers, no external posting. It means that any informations or support requests will be only posted from the new Forge, it will ensure the moderation activities and the archiving for further search.
    to
    Since my introduction into the System Team, I lead an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), an evolution will be carried out in order to: - Clarify the roles with their policies and restricted areas - Ensure the availability, the scalability and the security - Limit the needs for development or support (costs reduction) - Reduce the duplication and fragmentation of the content - Simplify the edition and administration tasks The main strategy is to reach a compromise between groups (specific needs) and tools (aggregation and integration). It results - Public -> Website reduced to its public area, no more registration except for editors. - Users -> New Forge for Users (repository + SCM) with its standalone authentication system and own bug tracking system. - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access by granting an administrator per institute. - System Team/external Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, discussion forum, forms, notifications, polls, private wikis, ...). Together, a transfer of the mailing lists '[Nemo]' & '[Nemo_st]' from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (French national network for education and research) is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address ('newsletter@nemo-ocean.eu'): open access but no posting allowed. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" ('systeam@nemo-ocean.eu'): subscription controlled by NEMO Officers, no external posting. It means that any informations or support requests will be only posted from the new Forge, it will ensure the moderation activities and the archiving for further search.

Changed on 2016-03-08T20:46:23+01:00 by nicolasmartin:

Changed on 2016-03-08T20:46:23+01:00 by nicolasmartin:

  • description changed from
    Since my introduction into the System Team, I lead for the year 2015 an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), an evolution will be carried out in order to: - Clarifying the roles, policies & areas - Ensuring the availability, the scalability and the security - Limiting needs for development or support (costs reduction) - Reducing the duplication and fragmentation of the content - Simplifying the edition and administration tasks The main strategy is to make a compromise between groups with specific needs / Tools aggregation and integration. It results - Public -> Website reduced to its public area, no more registration except for editors - Users -> New Forge for Users (repository + SCM) with its standalone authentication system and own bug tracking system. - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access - ST/Developers/Contributors/Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, private wikis, forms, discussion forum, ...) Together, a transfer of the mailing lists '[Nemo]' & '[Nemo_st]' from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (French national network for education and research) is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address ('newsletter@nemo-ocean.eu'): open access but no posting allowed. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" ('systeam@nemo-ocean.eu'): subscription controlled by NEMO Officers, no external posting. It means that any informations or support requests will be only posted from the new Forge, it will ensure the moderation and the archiving for further search.
    to
    Since my introduction into the System Team, I lead for the year 2015 an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), an evolution will be carried out in order to: - Clarifying the roles, policies & areas - Ensuring the availability, the scalability and the security - Limiting needs for development or support (costs reduction) - Reducing the duplication and fragmentation of the content - Simplifying the edition and administration tasks The main strategy is to make a compromise between groups with specific needs / Tools aggregation and integration. It results - Public -> Website reduced to its public area, no more registration except for editors - Users -> New Forge for Users (repository + SCM) with its standalone authentication system and own bug tracking system. - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access - ST/Developers/Contributors/Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, private wikis, forms, discussion forum, ...) Together, a transfer of the mailing lists '[Nemo]' & '[Nemo_st]' from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (French national network for education and research) is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address ('newsletter@nemo-ocean.eu'): open access but no posting allowed. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" ('systeam@nemo-ocean.eu'): subscription controlled by NEMO Officers, no external posting. It means that any informations or support requests will be only posted from the new Forge, it will ensure the moderation activities and the archiving for further search.

Changed on 2016-03-08T20:44:48+01:00 by nicolasmartin:

Changed on 2016-03-08T20:44:48+01:00 by nicolasmartin:

  • reviewers changed from Claire Levy to Claire Lévy
  • description changed from
    Since my introduction into the System Team, I lead for the year 2015 an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), an evolution will be in order to: - Clarifying the roles, policies & areas - Ensuring the availability, the scalability and the security - Limiting needs for development or support (costs reduction) - Reducing the duplication and fragmentation of the content - Simplifying the edition and administration tasks The main strategy is to make a compromise between groups with specific needs / Tools aggregation and integration. It results - Public -> Website reduced to its public area, no more registration except for editors - Users -> New Forge for Users (repository + SCM) with its standalone authentication system & own bug tracking system. - Developers -> Existing SVN repository on IPSL Forge with a widen and simplified access (ST, Developers, DevCom, Contributors, external Experts) - System Team -> Existing Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, private wikis, forms, discussion forum, ...) Together, a transfer of the mailing lists '[Nemo]' & '[Nemo_st]' from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (French national network for education and research) is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address ('newsletter@nemo-ocean.eu'): open access but no posting allowed from subscribers. - '[Nemo_st]' will become a confidential list with a hidden address ('systeam@nemo-ocean.eu'): subscription controlled by NEMO Officers, no external posting. It means that informations or support requests will only be
    to
    Since my introduction into the System Team, I lead for the year 2015 an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), an evolution will be carried out in order to: - Clarifying the roles, policies & areas - Ensuring the availability, the scalability and the security - Limiting needs for development or support (costs reduction) - Reducing the duplication and fragmentation of the content - Simplifying the edition and administration tasks The main strategy is to make a compromise between groups with specific needs / Tools aggregation and integration. It results - Public -> Website reduced to its public area, no more registration except for editors - Users -> New Forge for Users (repository + SCM) with its standalone authentication system and own bug tracking system. - Developers/Contributors -> Existing SVN repository on IPSL Forge with a widen and simplified access - ST/Developers/Contributors/Experts -> "" Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, private wikis, forms, discussion forum, ...) Together, a transfer of the mailing lists '[Nemo]' & '[Nemo_st]' from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (French national network for education and research) is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address ('newsletter@nemo-ocean.eu'): open access but no posting allowed. - '[Nemo_st]' "" "" " confidential list "" " hidden "" "" ('systeam@nemo-ocean.eu'): subscription controlled by NEMO Officers, no external posting. It means that any informations or support requests will be only posted from the new Forge, it will ensure the moderation and the archiving for further search.

Changed on 2016-03-08T19:44:29+01:00 by nicolasmartin:

Changed on 2016-03-08T19:44:29+01:00 by nicolasmartin:

  • implementation changed from
    - Website - Trac Trac becomes the only management portal NEMO officers granted - Forge NEMO officers granted as administrators for the project - Mailing lists NEMO officers granted as '[Nemo_st]' mailing list administrators
    to
    - Website - Trac NEMO officers granted - IPSL Forge NEMO officers granted as administrators for the project - Mailing lists NEMO officers granted as '[Nemo_st]' administrators
  • description changed from
    In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), an overall review on the different components of the current Collaborative Development Environment (CDE) The will be in order to: - Clarifying the roles, policies & areas - Ensuring the availability, the scalability and the security - Limiting needs for development or support (costs reduction) - Reducing the duplication and fragmentation of the content - Simplifying the edition and administration tasks The main strategy is to make a compromise between groups with specific needs / Tools aggregation and integration. It results - Public -> Website - Users -> New Forge for users - Developers -> Existing repository on IPSL Forge - System Team -> Existing Trac SCM on IPSL Forge (Website, Forge & Mailing lists) Website reduced to its public area Trac becomes the only management portal - Forge - Mailing lists
    to
    Since my introduction into the System Team, I lead for the year 2015 an overall review on the different components of the current Collaborative Development Environment (CDE). In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), an evolution will be in order to: - Clarifying the roles, policies & areas - Ensuring the availability, the scalability and the security - Limiting needs for development or support (costs reduction) - Reducing the duplication and fragmentation of the content - Simplifying the edition and administration tasks The main strategy is to make a compromise between groups with specific needs / Tools aggregation and integration. It results - Public -> Website reduced to its public area, no more registration except for editors - Users -> New Forge for Users (repository + SCM) with its standalone authentication system & own bug tracking system. - Developers -> Existing SVN repository on IPSL Forge with a widen and simplified access (ST, Developers, DevCom, Contributors, external Experts) - System Team -> Existing Trac SCM on IPSL Forge will become the only management portal by upgrading its features (agenda, private wikis, forms, discussion forum, ...) Together, a transfer of the mailing lists '[Nemo]' & '[Nemo_st]' from our local IT infrastructure to the hosted service 'Universalistes' by RENATER (French national network for education and research) is an opportunity to redefine their object and change their configuration: - '[Nemo]' will become a stringent newsletter with a custom address ('newsletter@nemo-ocean.eu'): open access but no posting allowed from subscribers. - '[Nemo_st]' will become a confidential list with a hidden address ('systeam@nemo-ocean.eu'): subscription controlled by NEMO Officers, no external posting. It means that informations or support requests will only be

Changed on 2016-03-08T18:06:39+01:00 by nicolasmartin:

Changed on 2016-03-08T18:06:39+01:00 by nicolasmartin:

  • implementation changed from
    - Website Website reduced to its public area - Trac Trac becomes the only management portal - Forge NEMO officers granted as administrators for the NEMO project installed - Mailing lists NEMO officers granted as '[Nemo_st]' mailing list administrators
    to
    - Website - Trac Trac becomes the only management portal NEMO officers granted - Forge NEMO officers granted as administrators for the project - Mailing lists NEMO officers granted as '[Nemo_st]' mailing list administrators
  • description changed from
    Modifications - Website Website reduced to its public area - Trac Trac becomes the only management portal - Forge NEMO officers granted as administrators for the NEMO project installed - Mailing lists NEMO officers granted as '[Nemo_st]' mailing list administrators
    to
    In anticipation of the end of life of the web server hosting the website (planned for Q1 2017), an overall review on the different components of the current Collaborative Development Environment (CDE) The will be in order to: - Clarifying the roles, policies & areas - Ensuring the availability, the scalability and the security - Limiting needs for development or support (costs reduction) - Reducing the duplication and fragmentation of the content - Simplifying the edition and administration tasks The main strategy is to make a compromise between groups with specific needs / Tools aggregation and integration. It results - Public -> Website - Users -> New Forge for users - Developers -> Existing repository on IPSL Forge - System Team -> Existing Trac SCM on IPSL Forge (Website, Forge & Mailing lists) Website reduced to its public area Trac becomes the only management portal - Forge - Mailing lists

Changed on 2016-03-08T17:12:34+01:00 by nicolasmartin:

Changed on 2016-03-08T17:12:34+01:00 by nicolasmartin:

  • implementation changed from
    This the implementation of the work.
    to
    - Website Website reduced to its public area - Trac Trac becomes the only management portal - Forge NEMO officers granted as administrators for the NEMO project installed - Mailing lists NEMO officers granted as '[Nemo_st]' mailing list administrators
  • manual changed from
    These are the updates for reference manual.
    to
    NR
  • description changed from
    This the description of the work.
    to
    Modifications - Website Website reduced to its public area - Trac Trac becomes the only management portal - Forge NEMO officers granted as administrators for the NEMO project installed - Mailing lists NEMO officers granted as '[Nemo_st]' mailing list administrators

Changed on 2016-03-04T18:46:43+01:00 by nicolasmartin:

Changed on 2016-03-04T18:46:43+01:00 by nicolasmartin:

  • implementation from default value set to This the implementation of the work.
  • manual from default value set to These are the updates for reference manual.
  • description from default value set to This the description of the work.

Changed on 2016-03-04T15:27:34+01:00 by nicolasmartin:

Changed on 2016-03-04T15:27:34+01:00 by nicolasmartin:

  • previewers changed from
    NEMO Officers
    to
    NEMO Officers (Clément Bricaud, Emanuela Clementi, Andrew Coward, Simona Flavoni, Dorotea Iovino & Tim Graham)

Changed on 2016-03-03T15:10:25+01:00 by nicolasmartin:

Changed on 2016-03-03T15:10:25+01:00 by nicolasmartin:

  • previewers changed from
    NEMO Officers (Clement Bricaud, Emanuela Clementi, Andrew Coward, Simona Flavoni, Dorotea Iovino & Tim Graham)
    to
    NEMO Officers

Changed on 2016-03-03T15:07:05+01:00 by nicolasmartin:

Changed on 2016-03-03T15:07:05+01:00 by nicolasmartin:

  • reviewers changed from Claire Lévy to Claire Levy
  • previewers changed from
    NEMO Officers (Clément Bricaud, Emanuela Clementi, Andrew Coward, Simona Flavoni, Dorotea Iovino & Tim Graham)
    to
    NEMO Officers (Clement Bricaud, Emanuela Clementi, Andrew Coward, Simona Flavoni, Dorotea Iovino & Tim Graham)

Changed on 2016-03-03T12:46:15+01:00 by nicolasmartin:

Changed on 2016-03-03T12:46:15+01:00 by nicolasmartin:

  • implementation Describe flow chart of the changes in the code. List the .F90 files and modules to be changed. Detailed list of new variables (including namelists) to be defined. Give for each the chosen name (following coding rules) and definition. reset to default value
  • previewers changed from
    NEMO Officers (Clément Bricaud, Emanuela Clementi, Andrew Coward, Simona Flavoni, Tim Graham, Dorotea Iovino)
    to
    NEMO Officers (Clément Bricaud, Emanuela Clementi, Andrew Coward, Simona Flavoni, Dorotea Iovino & Tim Graham)
  • ticket #1679 reset to default value
  • manual Using part 1 and 2, define the summary of changes to be done in the NEMO reference manual (tex files). reset to default value
  • description Describe the goal of development, and the methodology. Add reference documents or publications if relevant. reset to default value

Changed on 2016-02-24T18:23:02+01:00 by nicolasmartin:

Changed on 2016-02-24T18:23:02+01:00 by nicolasmartin:

  • previewers from default value set to NEMO Officers (Clément Bricaud, Emanuela Clementi, Andrew Coward, Simona Flavoni, Tim Graham, Dorotea Iovino)

Changed on 2016-02-24T18:21:41+01:00 by nicolasmartin: