Re: [galaxy-dev] configuring auth_ldap for galaxy
Another galaxy + nginx + LDAP user here.
Iry,
I have it working as well with help from Galaxy Wiki docs and mailing list
archives. The configure options that were used to compile nginx:
--add-module=../nginx-auth-ldap.20130823
--add-module=../nginx-upload-module-2.2 --with-pcre=../pcre-8.33
--with-http_ssl_module --conf-path=/usr/local/etc/nginx/nginx.conf
--pid-path=/var/run/nginx.pid --error-log-path=/var/log/nginx/error.log
--http-log-path=/var/log/nginx/access.log --user=galaxy-qa
--group=galaxy-qa --with-debug
I also supplied the proxy_set_header X-URL-SCHEME https; directive in
the / and /api location blocks.
Good luck!
John,
Thanks for the detailed response to Iry's question, and docs for this
setup.
Related question: Are you aware of a mechanism that would transmit LDAP
attributes, say mail for example, to downstream apps ? I have that
question in to the author of that module and haven't heard back.
The need for that: in my use case, the email address associated with
remote_user is not remote_u...@example.com but rather
first_name-last_n...@example.com. As such, I am stuck, less than
ideally, with requiring users to use first_name-last_n...@example.com as
their username instead of just short_name. Our previous solution to this
was to hack galaxy-dist/lib/galaxy/web/framework/__init__.py which I would
like to avoid for ease of maintainability purposes.
Thank you.
-Original Message-
From: John Chilton chil...@msi.umn.edu
Date: Wednesday, September 18, 2013 7:49 AM
To: Iry Witham iry.wit...@jax.org
Cc: galaxy-dev@lists.bx.psu.edu galaxy-dev@lists.bx.psu.edu
Subject: Re: [galaxy-dev] configuring auth_ldap for galaxy
You have to compile nginx with the auth-ldap module. Have you done
this? I am doing using CloudBioLinux and here is how it is being done
in that context, but it would probably be easier just doing it by
hand:
https://github.com/chapmanb/cloudbiolinux/blob/master/cloudbio/galaxy/__in
it__.py
I have posted my information on configuring CloudMan's nginx for LDAP
auth, but you can ignore the CloudMan stuff:
https://production-galaxy-instances-with-cloudman-and-cloudbiolinux.readth
edocs.org/en/latest/#configuring-nginx-conf
http {
auth_ldap_url
ldap://ldap.example.com/dc=example,dc=com?uid?sub?(objectClass=person);
#auth_ldap_binddn cn=nginx,ou=service,dc=example,dc=com;
#auth_ldap_binddn_passwd mYsUperPas55W0Rd
#auth_ldap_group_attribute uniquemember; # default 'member'
#auth_ldap_group_attribute_is_dn on; # default on
...
}
location / {
auth_ldap_require valid_user;
auth_ldap LDAP Auth Source Description;
proxy_set_header REMOTE_USER $remote_user;
proxy_pass http://galaxy_app;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-URL-SCHEME https;
...
}
# For API access, set REMOTE_USER if available so Galaxy
# session based requests are let through, if REMOTE_USER is not
# available pass the request through and let Galaxy determine
# if a key is present and valid.
location /api {
proxy_set_header REMOTE_USER $remote_user;
proxy_pass http://galaxy_app;
proxy_set_header X-Forwarded-Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}
-John
On Wed, Sep 18, 2013 at 7:37 AM, Iry Witham iry.wit...@jax.org wrote:
Hi Team,
Has anyone had any experience with setting up auth_ldap for nginx? I am
attempting to make this work, but nginx fails to start with the
following
message:
Starting nginx nginx: [emerg] unknown directive auth_ldap_url in
/usr/local/nginx/conf/nginx.conf:48
startproc: exit status of parent of /usr/local/nginx/sbin/nginx: 1
failed
Any help would be appreciated.
Thanks,
Iry Witham
The information in this email, including attachments, may be
confidential
and is intended solely for the addressee(s). If you believe you received
this email by mistake, please notify the sender by return email as soon
as
possible.
___
Please keep all replies on the list by using reply all
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
http://lists.bx.psu.edu/
To search Galaxy mailing lists use the unified search at:
http://galaxyproject.org/search/mailinglists/
___
Please keep all replies on the list by using reply all
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
http://lists.bx.psu.edu/
To search Galaxy mailing lists use the unified search at:
http://galaxyproject.org/search/mailinglists/
___
Please keep all replies on the list by using reply all
in your mail client. To manage your subscriptions to this
and other Galaxy lists, please use the interface at:
Re: [galaxy-dev] Login hook
Hi Adam, I appreciate your taking the time to provide detailed inputs along with links to relevant posts. Our instance is currently set up to allow users to self-service account provisioning in that if they are are a member of the University and have an appropriate entry in our LDAP/AD system, the act of providing their authentication credentials at the Galaxy login prompt results in the Galaxy account and a local OS-level account (only used for sFTP) being provisioned automagically via the aforementioned script invoked from a modified version of ../lib/galaxy/web/framework/__init__.py creating a local account and the requisite FTP upload directory if those don't already exist. As you rightly pointed out keeping code customizations current with upgrades is non-trivial and something I would like to minimize, and therefore this post. At this juncture, I will pursue the Shell/Python script polling galaxy_user option or re-attempt the ProFTPD (which appears to not require the creation of a local user account and has the ability to query the PostgreSQL DB for user credentials; in our case the credentials would have to be put together from a combination of PostgreSQL and LDAP queries) option. Thank you. -Original Message- From: Adam Brenner aebre...@uci.edu Date: Monday, August 26, 2013 12:45 PM To: Srinivas Maddhi srinivas-mad...@uiowa.edu Cc: Galaxy Dev galaxy-...@bx.psu.edu Subject: Re: [galaxy-dev] Login hook I am not aware of Galaxy having any sort of login hook as you described --- without writing custom code. This brings up the added challenge of keeping your custom modifications current with the latest release of galaxy. Another approach, and I am not sure how feasible this is on your setup, is to create all these added services during the user creation[1] process. On our HPC cluster this is the method we implemented. All our users can use SFTP, rsync, BBCP, etc to upload to the cluster and the user moves their data to galaxy by the FTP Trick[2] to their dropbox folder that galaxy has access to. Once data is moved to the dropbox folder, users login via the galaxy web interface and select the data via the Get Data - Upload File interface. This might be a simpler approach, create these services for each new user during their account creation. You will be forced to use the command line interface to create new users, but I believe its far simpler then using postgres notify or the other methods you described. [1]: http://dev.list.galaxyproject.org/user-creation-using-API-td4657726.html [2]: http://dev.list.galaxyproject.org/user-names-with-authentication-td4659271 .html -- Adam Brenner Computer Science, Undergraduate Student Donald Bren School of Information and Computer Sciences Research Computing Support Office of Information Technology http://www.oit.uci.edu/rcs/ University of California, Irvine www.ics.uci.edu/~aebrenne/ aebre...@uci.edu On Sun, Aug 25, 2013 at 9:39 AM, Maddhi, Srinivas srinivas-mad...@uiowa.edu wrote: Hello, Does Galaxy provide a post-login hook that could be used to trigger an operating system level action upon successful login ? Here is the scenario and use-case where that would come in handy: * Local instance of Galaxy (Nov 2012 release) on a Linux server with a PostgreSQL DB * Upload via FTP feature is enabled * Users are authenticated via LDAP and nginx * Users should be able to securely upload files (to their sub-directory within the configured FTP upload directory) The current method being employed to fulfill this use-case is through a modification to Š/galaxy-dist/lib/galaxy/web/framework/__init__.py file that calls a a shell script which creates an OS-level user and associated FTP upload directory. Files are uploaded by users via sFTP (SSHD configured to restrict Galaxy users to a chroot'ed directory). Options considered: * Shell/Python script that periodically queries the galaxy_user table and creates an OS-level user and FTP upload directory (not yet tried; introduces delay between user creation and FTP capability unless frequency of polling is high) * ProFTPD with sFTP and LDAP modules (increased administrative overhead compared to using built-in SSHD; wasn't able to get auto directory creation to work due to TBD cause) * PostgreSQL listen-notify to call a sFTP user creation script when an insert occurs in the galaxy_user table (not yet tried) Thank you. -- Senior Systems Administrator Iowa Institute for Human Genetics ITS Research Services, The University of Iowa ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/ ___ Please keep all replies
[galaxy-dev] Login hook
Hello, Does Galaxy provide a post-login hook that could be used to trigger an operating system level action upon successful login ? Here is the scenario and use-case where that would come in handy: * Local instance of Galaxy (Nov 2012 release) on a Linux server with a PostgreSQL DB * Upload via FTP feature is enabled * Users are authenticated via LDAP and nginx * Users should be able to securely upload files (to their sub-directory within the configured FTP upload directory) The current method being employed to fulfill this use-case is through a modification to Š/galaxy-dist/lib/galaxy/web/framework/__init__.py file that calls a a shell script which creates an OS-level user and associated FTP upload directory. Files are uploaded by users via sFTP (SSHD configured to restrict Galaxy users to a chroot'ed directory). Options considered: * Shell/Python script that periodically queries the galaxy_user table and creates an OS-level user and FTP upload directory (not yet tried; introduces delay between user creation and FTP capability unless frequency of polling is high) * ProFTPD with sFTP and LDAP modules (increased administrative overhead compared to using built-in SSHD; wasn't able to get auto directory creation to work due to TBD cause) * PostgreSQL listen-notify to call a sFTP user creation script when an insert occurs in the galaxy_user table (not yet tried) Thank you. -- Senior Systems Administrator Iowa Institute for Human Genetics ITS Research Services, The University of Iowa ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
Re: [galaxy-dev] Bowtie2 error: Creates a 62 kb file.
[Copying the list]. -Original Message- From: Maddhi, Srinivas Maddhi srinivas-mad...@uiowa.edu Date: Wednesday, July 24, 2013 10:01 AM To: Perez, Ricardo ricky_...@neo.tamu.edu Subject: Re: [galaxy-dev] Bowtie2 error: Creates a 62 kb file. Hi Ricardo, Ensuring that the appropriate reference indices are present, properly configured and selected when running bowtie2 might help address this problem. -Original Message- From: Perez, Ricardo ricky_...@neo.tamu.edu Date: Wednesday, July 24, 2013 1:35 AM To: galaxy-dev@lists.bx.psu.edu galaxy-dev@lists.bx.psu.edu Subject: [galaxy-dev] Bowtie2 error: Creates a 62 kb file. Dear all, Today we ran some problems when running bowtie2. When we run bowtie2, the run manages to complete. However, bowtie2 creates a 62kb file. The error log that we get is the following: galaxy.jobs DEBUG 2013-07-23 17:09:42,378 (1483) Persisting job destination (destination id: local:///) galaxy.jobs.handler INFO 2013-07-23 17:09:42,392 (1483) Job dispatched galaxy.tools DEBUG 2013-07-23 17:09:42,556 Building dependency shell command for dependency 'bowtie2' galaxy.tools WARNING 2013-07-23 17:09:42,556 Failed to resolve dependency on 'bowtie2', ignoring galaxy.tools DEBUG 2013-07-23 17:09:42,556 Building dependency shell command for dependency 'samtools' galaxy.tools WARNING 2013-07-23 17:09:42,556 Failed to resolve dependency on 'samtools', ignoring galaxy.jobs.runners.local DEBUG 2013-07-23 17:09:42,626 (1483) executing: bowtie2 --version /usr/local/galaxy/galaxy-dist/database/tmp/GALAXY_VERSION_STRING_1483; python /usr/local/galaxy/galaxy-dist/tools/sr_mapping/bowtie2_wrapper.py --num-threads=4 --output=/usr/local/galaxy/galaxy-dist/database/files/001/dataset_1673.da t --indexes-path=/data/db/fungidb/Ncrassa_OR74A/bowtie2/Ncrassa_wt_Chr01.C h r07.+ChrM.+rDNA_v12 --single-paired=paired --input1=/usr/local/galaxy/galaxy-dist/database/files/001/dataset_1668.da t --input2=/usr/local/galaxy/galaxy-dist/database/files/001/dataset_1669.da t -I 0 -X 250 --settings=preSet galaxy.jobs DEBUG 2013-07-23 17:09:42,696 (1483) Persisting job destination (destination id: local:///) galaxy.jobs.runners.local DEBUG 2013-07-23 17:09:42,766 execution finished: bowtie2 --version /usr/local/galaxy/galaxy-dist/database/tmp/GALAXY_VERSION_STRING_1483; python /usr/local/galaxy/galaxy-dist/tools/sr_mapping/bowtie2_wrapper.py --num-threads=4 --output=/usr/local/galaxy/galaxy-dist/database/files/001/dataset_1673.da t --indexes-path=/data/db/fungidb/Ncrassa_OR74A/bowtie2/Ncrassa_wt_Chr01.C h r07.+ChrM.+rDNA_v12 --single-paired=paired --input1=/usr/local/galaxy/galaxy-dist/database/files/001/dataset_1668.da t --input2=/usr/local/galaxy/galaxy-dist/database/files/001/dataset_1669.da t -I 0 -X 250 --settings=preSet galaxy.jobs.runners DEBUG 2013-07-23 17:09:42,850 executing external set_meta script for job 1483: /usr/local/galaxy/galaxy-dist/set_metadata.sh ./database/files /usr/local/galaxy/galaxy-dist/database/job_working_directory/001/1483 . /usr/local/galaxy/galaxy-dist/universe_wsgi.ini /usr/local/galaxy/galaxy-dist/database/tmp/tmpUiqpPD /usr/local/galaxy/galaxy-dist/database/job_working_directory/001/1483/gal a xy.json /usr/local/galaxy/galaxy-dist/database/job_working_directory/001/1483/met a data_in_HistoryDatasetAssociation_1767_wqhEmr,/usr/local/galaxy/galaxy-di s t/database/job_working_directory/001/1483/metadata_kwds_HistoryDatasetAss o ciation_1767_qVZjpG,/usr/local/galaxy/galaxy-dist/database/job_working_di r ectory/001/1483/metadata_out_HistoryDatasetAssociation_1767_vIfpRO,/usr/l o cal/galaxy/galaxy-dist/database/job_working_directory/001/1483/metadata_r e sults_HistoryDatasetAssociation_1767_UNl6OR,,/usr/local/galaxy/galaxy-dis t /database/job_working_directory/001/1483/metadata_over! ride_HistoryDatasetAssociation_1767_MZilrL 165.91.11.135 - - [23/Jul/2013:17:09:43 -0500] GET /api/histories/ca8efa3c47500414 HTTP/1.1 200 - http://galaxy.tamu.edu/history; Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.22 (KHTML, like Gecko) Ubuntu Chromium/25.0.1364.160 Chrome/25.0.1364.160 Safari/537.22 165.91.11.231 - - [23/Jul/2013:17:09:43 -0500] GET /history HTTP/1.1 200 - http://galaxy.tamu.edu/tool_runner/index; Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.71 Safari/537.36 165.91.11.231 - - [23/Jul/2013:17:09:43 -0500] GET /api/histories/1ab12f1e464820dd HTTP/1.1 200 - http://galaxy.tamu.edu/history; Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/28.0.1500.71 Safari/537.36 165.91.11.231 - - [23/Jul/2013:17:09:43 -0500] GET /history/get_display_application_links HTTP/1.1 200 - http://galaxy.tamu.edu/history; Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/537.36 (KHTML, like Gecko
Re: [galaxy-dev] Short-term access to a galaxy server for teaching
Hi Max, An alternative approach, in case that becomes necessary, would be to set up your own temporary instance of Galaxy in the Amazon Web Services (AWS) Cloud as described at http://wiki.galaxyproject.org/CloudMan. Another Cloud-based option: if interested in installing Galaxy on an auto-scaling HPC cluster in the AWS Cloud from the command line, I can provide the instructions to do so. The instructions were designed to allow those with access to a browser on a Linux, Mac or Windows [1] system and minimal computing experience perform the installation. Time to get Galaxy up and running using this method is estimated at one to two hours. Good luck! Notes: 1. Will require installation of Putty or similar program for secure access to the AWS virtual machine, 2. Both options mentioned above could be overkill, although eminently feasible, if all you need is Galaxy running on a single server, 3. Additional options are listed at http://wiki.galaxyproject.org/Big%20Picture/Choices -- Srinivas Maddhi Senior Systems Administrator Iowa Institute for Human Genetics ITS Research Services, The University of Iowa -Original Message- From: Max Heiman hei...@genetics.med.harvard.edu Date: Thursday, July 11, 2013 9:16 AM To: galaxy-...@bx.psu.edu galaxy-...@bx.psu.edu Subject: [galaxy-dev] Short-term access to a galaxy server for teaching Hi, We would like to use Galaxy to introduce genomic analysis in our introductory graduate genetics course. Would anyone be willing to let us borrow a server for two hours (9-11 am Boston time, Sept 25)? The students will be uploading ~1M 30-bp reads, running QC and trimming barcodes, using BOWTIE to align them to the yeast genome and then MACS to call peaks. There will be about 40 users total. Each task runs quickly on the public server, but we are concerned about the queue times when dealing with a 90-min class. Thank you for any help or advice, best Max ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
Re: [galaxy-dev] GalaxyAdmins Group: Future Directions?
Third, should we start a separate email list for GalaxyAdmins business? It would have far fewer members and have far less traffic than Galaxy-Dev. I'm in favor of it. If you have an opinion, please post here. May want to wait until after we determine the future direction for the group unless the overhead in creating and maintaining it is low. From: Dave Clements cleme...@galaxyproject.orgmailto:cleme...@galaxyproject.org Date: Wednesday, April 24, 2013 12:55 PM To: Srinivas Maddhi srinivas-mad...@uiowa.edumailto:srinivas-mad...@uiowa.edu Cc: Hans-Rudolf Hotz h...@fmi.chmailto:h...@fmi.ch, Galaxy Dev List galaxy-...@bx.psu.edumailto:galaxy-...@bx.psu.edu Subject: Re: [galaxy-dev] GalaxyAdmins Group: Future Directions? Hello all, Just some minor updates to refresh this thread. Most of this will be described in more detail in separate emails over the next two weeks. First, the next web meetup will be May 15. We haven't nailed down a main speaker yet, but Dannon Baker will be giving the project update. Second, I've created a Birds-of-a-Feather (BoF) session at GCC2013 to continue, and maybe just finish, this discussion in person at the meeting (see http://wiki.galaxyproject.org/Events/GCC2013/BoF/GalaxyAdmins). If you are interested in participating in that BoF, either send me an email, or add your name to that wiki page. (We will officially announce GCC2013 BoFs in a few weeks - after the poster abstract deadline, but feel free to get a head start and add your own now. :-) Third, should we start a separate email list for GalaxyAdmins business? It would have far fewer members and have far less traffic than Galaxy-Dev. I'm in favor of it. If you have an opinion, please post here. Thanks, Dave C On Wed, Apr 10, 2013 at 1:32 PM, Dave Clements cleme...@galaxyproject.orgmailto:cleme...@galaxyproject.org wrote: Hello all, First, thanks to Srinivas and Hans for the responses. I have kept track of the head counts for most meetups: 2012/07/07 27 2012/07/27 ? (in person meetup at GCC2012) 2012/09/19 10 2012/11/07 17 2013/01/16 14 2013/03/20 15 So, maybe converging on mid-teens? This number is not as high as I had hoped. Srinivas, is there any way to tell how many times the screencasts have been watched afterword? I'm see the group as complimentary to Galaxy-Dev, and I am leaning towards creating a Galaxy-Admins maling list that is purely about the group and group activities (Ann BZ's idea originally). It would not be a support channel and any stray support postings would get redirected to Galaxy-Dev (or Galaxy-User, if that's where they belong). We would still post activities to Galaxy-Dev as well, but any group business (like this discussion) would happen only on Galaxy-Admins. On the group leadership issue I very much want the group to be led by people that are not part of the core team. I am quite willing to continue to fill the supportive role I've been doing for the past year. If GalaxyAdmins is to become a voice for the community at some point in the future, it should very definitely not be led by the core team. However, if our future consists only of bi-monthly meetups (which have been great!) then it does not matter as much. My 2p, Dave C On Tue, Apr 9, 2013 at 4:58 PM, Maddhi, Srinivas srinivas-mad...@uiowa.edumailto:srinivas-mad...@uiowa.edu wrote: Hi Hans, Thanks for the response. I didn't mean to advocate for an overlapping group but rather to identify means to strengthen the existing dev and user group interactions. There might, however, be some value in evaluating whether we are at a point, in terms of number of deployment and support models for the same, wherein a Galaxy admin specific group or mailing list would make sense. We have had an estimated six to ten participants at the meet-ups that have occurred since September 2012. Best regards, Srinivas. -Original Message- From: Hans-Rudolf Hotz h...@fmi.chmailto:h...@fmi.ch Date: Monday, April 8, 2013 3:21 AM To: Srinivas Maddhi srinivas-mad...@uiowa.edumailto:srinivas-mad...@uiowa.edu, Dave Clements cleme...@galaxyproject.orgmailto:cleme...@galaxyproject.org Cc: Galaxy Dev List galaxy-...@bx.psu.edumailto:galaxy-...@bx.psu.edu Subject: Re: [galaxy-dev] GalaxyAdmins Group: Future Directions? Hi Srinivas Thank you very much for e-mail...and thereby reminding me that I haven't replied to Dave's call a week ago. I second most of your thoughts. However, I am not sure of the idea of creating a full-fledged user group with additional opportunities for sharing, learning and collaborating. I like it, but how do you intend to distinguish this group from the current '[galaxy-dev]' group/community? I am afraid stuff will get lost between the two groups or it leads to duplication.probably something we need to discuss in Oslo? I am definitively in favor of a dual leadership - one person from the admin community and one from the Galaxy team. Regards, Hans
Re: [galaxy-dev] GalaxyAdmins Group: Future Directions?
Hi Hans, Thanks for the response. I didn't mean to advocate for an overlapping group but rather to identify means to strengthen the existing dev and user group interactions. There might, however, be some value in evaluating whether we are at a point, in terms of number of deployment and support models for the same, wherein a Galaxy admin specific group or mailing list would make sense. We have had an estimated six to ten participants at the meet-ups that have occurred since September 2012. Best regards, Srinivas. -Original Message- From: Hans-Rudolf Hotz h...@fmi.ch Date: Monday, April 8, 2013 3:21 AM To: Srinivas Maddhi srinivas-mad...@uiowa.edu, Dave Clements cleme...@galaxyproject.org Cc: Galaxy Dev List galaxy-...@bx.psu.edu Subject: Re: [galaxy-dev] GalaxyAdmins Group: Future Directions? Hi Srinivas Thank you very much for e-mail...and thereby reminding me that I haven't replied to Dave's call a week ago. I second most of your thoughts. However, I am not sure of the idea of creating a full-fledged user group with additional opportunities for sharing, learning and collaborating. I like it, but how do you intend to distinguish this group from the current '[galaxy-dev]' group/community? I am afraid stuff will get lost between the two groups or it leads to duplication.probably something we need to discuss in Oslo? I am definitively in favor of a dual leadership - one person from the admin community and one from the Galaxy team. Regards, Hans-Rudolf PS: Do you have stats of who (or how many) has taken part in the past meetups? I think the numbers have been much smaller than the number of responses to Ann's original proposal last April. On 04/05/2013 10:43 PM, Maddhi, Srinivas wrote: Hello, Based on my observations and interactions during the past few meet-ups and as an administrator of Galaxy, the current goals of the group [1] remain relevant and are being met through the meet-ups. An additional benefit to these meet-ups that has evolved is an update from a member of the Galaxy team on upcoming features and other developments. With regard to the future of the group, my suggestion is to keep it going and work towards building a full-fledged user group with additional opportunities for sharing, learning and collaborating. This will strengthen the community, possibly drive increased adoption, and further serve to guide development of Galaxy. Appointing one of more leaders (one each from the Galaxy team and user community) to identify speakers, drive the agenda, set a cadence to the meet-ups and drive the formation of a user group would be helpful, IMHO. Thanks! Notes: 1. Build a community, learn from each other From: Dave Clements cleme...@galaxyproject.org mailto:cleme...@galaxyproject.org Date: Monday, April 1, 2013 11:07 AM To: Galaxy Dev List galaxy-...@bx.psu.edu mailto:galaxy-...@bx.psu.edu Subject: [galaxy-dev] GalaxyAdmins Group: Future Directions? Hello all, The GalaxyAdmins group is coming up on it's one year anniversary (coinciding with GCC2013) and this is a good opportunity to discuss what the future of the group should be. Some starting topics for discussion are on the GalaxyAdmins Future Directions page (http://wiki.galaxyproject.org/Community/GalaxyAdmins/Future). These include * What should the group's goals and activities be? * What type of leadership structure should the group have, and how should it be selected? The discussion, however, is wide open to any topic relevant to the group. If you have any opinions or suggestions please reply to the group. Anyone with an interest in the group is encouraged to post. Once the discussion settles, I will summarize the discussion on the wiki page and suggest an action plan for making those things happen. Thanks, Dave C. -- http://galaxyproject.org/GCC2013 http://galaxyproject.org/ http://getgalaxy.org/ http://usegalaxy.org/ http://wiki.galaxyproject.org/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
Re: [galaxy-dev] GalaxyAdmins Group: Future Directions?
Hello, Based on my observations and interactions during the past few meet-ups and as an administrator of Galaxy, the current goals of the group [1] remain relevant and are being met through the meet-ups. An additional benefit to these meet-ups that has evolved is an update from a member of the Galaxy team on upcoming features and other developments. With regard to the future of the group, my suggestion is to keep it going and work towards building a full-fledged user group with additional opportunities for sharing, learning and collaborating. This will strengthen the community, possibly drive increased adoption, and further serve to guide development of Galaxy. Appointing one of more leaders (one each from the Galaxy team and user community) to identify speakers, drive the agenda, set a cadence to the meet-ups and drive the formation of a user group would be helpful, IMHO. Thanks! Notes: 1. Build a community, learn from each other From: Dave Clements cleme...@galaxyproject.orgmailto:cleme...@galaxyproject.org Date: Monday, April 1, 2013 11:07 AM To: Galaxy Dev List galaxy-...@bx.psu.edumailto:galaxy-...@bx.psu.edu Subject: [galaxy-dev] GalaxyAdmins Group: Future Directions? Hello all, The GalaxyAdmins group is coming up on it's one year anniversary (coinciding with GCC2013) and this is a good opportunity to discuss what the future of the group should be. Some starting topics for discussion are on the GalaxyAdmins Future Directions page (http://wiki.galaxyproject.org/Community/GalaxyAdmins/Future). These include * What should the group's goals and activities be? * What type of leadership structure should the group have, and how should it be selected? The discussion, however, is wide open to any topic relevant to the group. If you have any opinions or suggestions please reply to the group. Anyone with an interest in the group is encouraged to post. Once the discussion settles, I will summarize the discussion on the wiki page and suggest an action plan for making those things happen. Thanks, Dave C. -- http://galaxyproject.org/GCC2013 http://galaxyproject.org/ http://getgalaxy.org/ http://usegalaxy.org/ http://wiki.galaxyproject.org/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ To search Galaxy mailing lists use the unified search at: http://galaxyproject.org/search/mailinglists/
