corinnekrych
corinnekrych
To help the user understand the initial talk created is a "draft" before being submitted (ie: push to a conference and being visible to organizers), I'd propose 2 main chnages:...
Actually the communication organizer => speaker by email is good. but we're also missing speaker => organizer. If a speaker want s to give information or ask question during submission,...
Actually, you can revisit the message to committee afterwards by sbmitting again your modified talk.  What is not very intuitive is that you have to "submit" your talk again...
All valid points, the more I look into templatized resource creation (trying to finish WIP PR), the more I wonder if plain go struct wouldn't be easier. :) Let's me...
Here are the PR: - with template (not completed yet) https://github.com/redhat-developer/devopsconsole-operator/pull/10 - with go struct https://github.com/redhat-developer/devopsconsole-operator/pull/13
http://localhost:8080/ng-templates/alert.html http://localhost:8080/toto2/person/indexlist causing a 404
indeed fix #17 is just fine not need to use root context any more. Still a 404 on http://localhost:8080/toto2/person/indexlist http://localhost:8080/toto2/person/indexsave I initially supposed the problem was located in index.gsp generated...
> > > $('body').data('base-url') > > > "/toto2/person/index"
Here 's my demo exemple (one of them). nothing much... 2012/7/3 Rob Fletcher < [email protected] > Can run this command in the javascript console and let me know what the...