Deployments in Sahana Sunflower
27 views
Skip to first unread message
Michael Howden
May 30, 2014, 1:09:48 AM5/30/14
to Sahana Eden
Hi All,
The topic of recording deployments in Sahana Sunflower came up in our last meeting.
One of the goals of Sunflower was to " To publish information about all Sahana deployments". IMHO this is something that we could do a better job. We have a lot of information about deployments spread over a number places:
http://eden.sahanafoundation.org/wiki/BluePrint/Sunflower#DeploymentsPage
The topic of recording deployments in Sahana Sunflower came up in our last meeting.
One of the goals of Sunflower was to " To publish information about all Sahana deployments". IMHO this is something that we could do a better job. We have a lot of information about deployments spread over a number places:
- http://eden.sahanafoundation.org/wiki/Deployments
- http://wiki.sahanafoundation.org/deployments/start
- http://sahanafoundation.org/about-us/deployments/
http://eden.sahanafoundation.org/wiki/BluePrint/Sunflower#DeploymentsPage
- Eventually I'd like to see our website
(http://sahanafoundation.org/about-us/deployments/) pulling
custom designed pages from Sunflower
- I'm currently thinking that the deployment information can be stored in the project_project data model. Somay - if you need additional fields these could be added to a linked table project_deployment (but check that there's not a field already)
- EVERYONE: What would you like to know currently about Sahana Deployments?
- Who is the audience of the Deployments pages? I see these as
"first-tier" general introduction / promotion material, with
more expansive information record elsewhere and linked to. I
would still see the wiki pages as having detailed "working"
information about the projects. Dominic would like to see
deployments pages have more information such as the goal of the
deployment (Dominic - please feel free to correct/elaborate)
- What does everyone think of the Call to Action buttons - are
we missing anything? These might not always be available as not
all deployments will be managed with tasks in Sunflower:
- Test Deployment (List of Tasks)
- Report Bug (Create Tasks)
- Fix Bug (List of Tasks)
- Implement Feature (List of Tasks)
- Somay - I think that these calls to action should be mirrored on the homepage
Have a great weekend all!
--
Michael Howden
Director, Sahana Software Foundation
Managing Director, AidIQ
mic...@sahanafoundation.org
skype: michael.howden
+64 (21) 126-1360
+1 (213) 261-4250
twitter:@michaelhowden
Michael Howden
Director, Sahana Software Foundation
Managing Director, AidIQ
mic...@sahanafoundation.org
skype: michael.howden
+64 (21) 126-1360
+1 (213) 261-4250
twitter:@michaelhowden
Dominic König
May 30, 2014, 5:05:19 AM5/30/14
to sahan...@googlegroups.com, Michael Howden
I think that for external "visitors" the SSF homepage would be the first place
to look for information on deployments.
This should contain only minimal information like time and place, purpose,
stakeholders, and maybe some review/comments from stakeholders - basically the
"cover story" telling when, where and by whom Sahana has been used and what
for - for marketing/promotion purposes. A map would be nice/handy there to find
deployments by location - where the overlay could come from a Sunflower feed,
and link to the particular blog entry / page on the SSF homepage.
Sunflower could then be the place to manage the related tasks and events (e.g.
code sprints, "hackathons", meetings) and contact information, and certainly
the "call for action" items - i.e. be the main entry point for contributors.
Same map there, but linking to the respective project page in Sunflower.
On the wiki, we should have all relevant "working information" such as project
descriptions, links to blue prints (requirements) and implementation details,
feature documentation etc. - a lot of living documents where we do need wiki
features including revision history and diff, easy editing and hypertext
linking to related information and so forth. No map needed here, I think.
Some deployments may even employ additional resources such as hackpads or
gDocs - that highly depends on the working mode (emergency?) and specific
requirements (e.g. some deployments may need collaborative drawing/mockup
tools), but eventually all that would be linked from the respective wiki
pages.
I don't see the advantage of "moving it all into Sunflower" - nor to put it all
under a common structure, nor do I actually see that we're doing a "bad job"
in communicating information about deployments? Who has complained?
Dominic
fredagen den 30 maj 2014 17.09.44 skrev Michael Howden:
> Hi All,
>
> The topic of recording deployments in Sahana Sunflower came up in our
> last meeting.
>
> One of the goals of Sunflower was to " To publish information about all
> Sahana deployments". IMHO this is something that we could do a better
> job. We have a lot of information about deployments spread over a number
> places:
>
> * http://eden.sahanafoundation.org/wiki/Deployments
> * http://wiki.sahanafoundation.org/deployments/start
> * http://sahanafoundation.org/about-us/deployments/
> Deployments?
> * Who is the audience of the Deployments pages? I see these as
> o Report Bug (Create Tasks)
> o Fix Bug (List of Tasks)
> o Implement Feature (List of Tasks)
> * Somay - I think that these calls to action should be mirrored on the
to look for information on deployments.
This should contain only minimal information like time and place, purpose,
stakeholders, and maybe some review/comments from stakeholders - basically the
"cover story" telling when, where and by whom Sahana has been used and what
for - for marketing/promotion purposes. A map would be nice/handy there to find
deployments by location - where the overlay could come from a Sunflower feed,
and link to the particular blog entry / page on the SSF homepage.
Sunflower could then be the place to manage the related tasks and events (e.g.
code sprints, "hackathons", meetings) and contact information, and certainly
the "call for action" items - i.e. be the main entry point for contributors.
Same map there, but linking to the respective project page in Sunflower.
On the wiki, we should have all relevant "working information" such as project
descriptions, links to blue prints (requirements) and implementation details,
feature documentation etc. - a lot of living documents where we do need wiki
features including revision history and diff, easy editing and hypertext
linking to related information and so forth. No map needed here, I think.
Some deployments may even employ additional resources such as hackpads or
gDocs - that highly depends on the working mode (emergency?) and specific
requirements (e.g. some deployments may need collaborative drawing/mockup
tools), but eventually all that would be linked from the respective wiki
pages.
I don't see the advantage of "moving it all into Sunflower" - nor to put it all
under a common structure, nor do I actually see that we're doing a "bad job"
in communicating information about deployments? Who has complained?
Dominic
fredagen den 30 maj 2014 17.09.44 skrev Michael Howden:
> Hi All,
>
> The topic of recording deployments in Sahana Sunflower came up in our
> last meeting.
>
> One of the goals of Sunflower was to " To publish information about all
> Sahana deployments". IMHO this is something that we could do a better
> job. We have a lot of information about deployments spread over a number
> places:
>
> * http://wiki.sahanafoundation.org/deployments/start
> * http://sahanafoundation.org/about-us/deployments/
>
> I personally feel that this information needs to be pulled together in a
> more structured manner and better presented - which is why I think that
> it would be great to have it in Sunflower. I've put together a design here:
> http://eden.sahanafoundation.org/wiki/BluePrint/Sunflower#DeploymentsPage
>
> * Eventually I'd like to see our website
> I personally feel that this information needs to be pulled together in a
> more structured manner and better presented - which is why I think that
> it would be great to have it in Sunflower. I've put together a design here:
> http://eden.sahanafoundation.org/wiki/BluePrint/Sunflower#DeploymentsPage
>
> (http://sahanafoundation.org/about-us/deployments/) pulling custom
> designed pages from Sunflower
> * I'm currently thinking that the deployment information can be stored
> designed pages from Sunflower
> in the project_project data model. Somay - if you need additional
> fields these could be added to a linked table project_deployment
> (but check that there's not a field already)
>
> Questions:
>
> * EVERYONE: What would you like to know currently about Sahana
> fields these could be added to a linked table project_deployment
> (but check that there's not a field already)
>
> Questions:
>
> Deployments?
> * Who is the audience of the Deployments pages? I see these as
> "first-tier" general introduction / promotion material, with more
> expansive information record elsewhere and linked to. I would still
> see the wiki pages as having detailed "working" information about
> the projects. Dominic would like to see deployments pages have more
> information such as the goal of the deployment (Dominic - please
> feel free to correct/elaborate)
> * What does everyone think of the Call to Action buttons - are we
> expansive information record elsewhere and linked to. I would still
> see the wiki pages as having detailed "working" information about
> the projects. Dominic would like to see deployments pages have more
> information such as the goal of the deployment (Dominic - please
> feel free to correct/elaborate)
> missing anything? These might not always be available as not all
> deployments will be managed with tasks in Sunflower:
> o Test Deployment (List of Tasks)
> deployments will be managed with tasks in Sunflower:
> o Report Bug (Create Tasks)
> o Fix Bug (List of Tasks)
> o Implement Feature (List of Tasks)
> * Somay - I think that these calls to action should be mirrored on the
Fran Boon
May 30, 2014, 5:25:06 AM5/30/14
to sahan...@googlegroups.com
On 30 May 2014 06:09, Michael Howden <mic...@sahanafoundation.org> wrote:
> EVERYONE: What would you like to know currently about Sahana Deployments?
> Who is the audience of the Deployments pages? I see these as "first-tier"
> general introduction / promotion material, with more expansive information
> record elsewhere and linked to. I would still see the wiki pages as having
> detailed "working" information about the projects. Dominic would like to see
> deployments pages have more information such as the goal of the deployment
> (Dominic - please feel free to correct/elaborate)
I like to use these as a reference when communicating internally about
> EVERYONE: What would you like to know currently about Sahana Deployments?
> Who is the audience of the Deployments pages? I see these as "first-tier"
> general introduction / promotion material, with more expansive information
> record elsewhere and linked to. I would still see the wiki pages as having
> detailed "working" information about the projects. Dominic would like to see
> deployments pages have more information such as the goal of the deployment
> (Dominic - please feel free to correct/elaborate)
users and their use cases...these can be borne in mind when having
design discussions about features.
More info the better.
Like Dominic, I can see value in basic details in Sunflower:
sufficient to allow Filtering of Tasks and drive a listing & map which
can be embedded on the main SSF site.
However I don't think this could/should fully replace other systems,
such as Blogs, Wiki pages &/or Hackpads/gDocs. The links can certainly
be stored in Sunflower too & thus be visible in the SSF site or from
the Sunflower task list (links in RHeader / Profile Header?)
F
Pat Tressel
May 31, 2014, 4:48:33 AM5/31/14
to sahan...@googlegroups.com
- EVERYONE: What would you like to know currently about Sahana Deployments?
I agree w/ Fran & Dominic that unstructured documents may be better for unstructured info, but there are some types of info that could well be stored in a structured table:
- Stakeholder contact info
- Support contact
- Sahana liaison
- Repo location or template
- Status
- Site
- Demo site
- Bug tracker (if they have their own)
-- Pat
Pat Tressel
May 31, 2014, 4:56:59 AM5/31/14
to sahan...@googlegroups.com
Forgot 2 say...
That's a specialized type of customer relationship management, so this may be a suggestion to add some form of CRM. That would typically include other info, which might not be relevant here, such as:
- Contact log
- Legal / contractual info
Once upon a time, we talked about automatically contacting anyone who downloaded / cloned the code. That could also auto-generate a rudimentary CRM entry.
-- Pat
Somay Jain
Jun 3, 2014, 1:07:22 PM6/3/14
to sahan...@googlegroups.com
On Friday, 30 May 2014 10:39:48 UTC+5:30, Michael Howden wrote:
Hi All,
The topic of recording deployments in Sahana Sunflower came up in our last meeting.
One of the goals of Sunflower was to " To publish information about all Sahana deployments". IMHO this is something that we could do a better job. We have a lot of information about deployments spread over a number places:
I personally feel that this information needs to be pulled together in a more structured manner and better presented - which is why I think that it would be great to have it in Sunflower. I've put together a design here:
- http://eden.sahanafoundation.org/wiki/Deployments
- http://wiki.sahanafoundation.org/deployments/start
- http://sahanafoundation.org/about-us/deployments/
http://eden.sahanafoundation.org/wiki/BluePrint/Sunflower#DeploymentsPage
- Eventually I'd like to see our website (http://sahanafoundation.org/about-us/deployments/) pulling custom designed pages from Sunflower
- I'm currently thinking that the deployment information can be stored in the project_project data model. Somay - if you need additional fields these could be added to a linked table project_deployment (but check that there's not a field already)
The design looks good!
IMHO, I too feel that deployments should be highlighted on the SSF homepage for the external visitors. The SSF homepage ought to have all the general information which a visitor would want to see. Sunflower should remain a community management tool. Ofcourse, we should have the basic details and tasks about the deployment in Sunflower, because that is also part of the community, but the general introduction/promotion material should be on the main SSF homepage.
Just a suggestion, if we are not able to customise wordpress that well (there was a discussion on this in the last meeting), we should give a try to porting our website to a more customisable format, like Jekyll. Jekyll is just a suggestion off the top of my head, but if it is worth, we could look into it in future.
Regards
Somay
Reply all
Reply to author
Forward
0 new messages