openstack team mailing list archive
-
openstack team
-
Mailing list archive
-
Message #25109
Re: [Horizon] [UX] phabriactor/pholio as a possible UX option
Hi!
Sorry - we've been a bit busy and this got put on the back burner. I
believe that ttx has done some work over the last couple of weeks ...
Theirry, any updates from your end?
Github as an option is problematic for several reasons. The ones that
come to mind are that it's not opensource, it doesn't integrate into any
of the rest of our tooling or SSO, and we're actually working to clarify
to people that we do not do our development on github, and adding the
usage of a github issue tracker somewhere would kindof undercut that.
So we're still trying to find an option that we can run that does work
for everyone. I will redouble those efforts.
We also have an effort underway to spin up an owncloud instance ... so
for filesharing needs that might be a choice.
On 07/12/2013 08:47 PM, Toshiyuki Hayashi wrote:
> Hi,
>
>> So far, my understanding is that requirements are:
>> - discussion
>> - messages containing images
>> - possibly specific image annotation/commenting
>
> Also if there is file sharing space, that would be great.
> e.g.)
> - photoshop template for designing and prototyping
> - html template for designing and prototyping
> - wireframe data (it seems Jaromir has created good one already :-) )
> - some document regarding UI
>
> Discourse seems good, but still Github is better for me.
> Why Github was evaluated as not suitable?
>
>
> On Tue, Jul 9, 2013 at 4:52 AM, Jaromir Coufal <jcoufal@xxxxxxxxxx> wrote:
>>
>> On 2013/27/06 09:37, Thierry Carrez wrote:
>>
>> As a data point, Discourse could also be a solution:
>> http://www.discourse.org/
>>
>> It's clearly a discussion tool (including pretty advanced threading,
>> post likes, etc.), and messages can contain images.
>>
>> See a design discussion for example at:
>> http://test.ubuntu-discourse.org/t/a-ubuntu-ish-theme-for-the-site/177
>>
>>
>> Discourse actually looks pretty good. I was playing around that a little bit
>> and like it. We can consider labels as categories - not optimal, but can
>> work if we have only design discussions. Only problem is that we might want
>> to extend the tool for other discussions as well and then it will be less
>> optimal.
>>
>> Do you guys see any other possibilities apart from this one?
>>
>> -- Jarda
>
>
>
Follow ups
References