On 16 February 2012 19:32, Michael Howden <mic...@sahanafoundation.org> wrote:
>> Currently the Sahanathon tasks are in a gSpreadsheet in the right format
>> to import into an Eden instance. If there are any bugs in Trac *which are
>> relevant to the Sahanathon* (of which I'm unaware of any) then they can be
>> added to this spreadsheet....however the Sahanathon is not (as far as I'm
>> aware) a general bugfixing.
> I would hope that this would happen as we start testing the solution.
Only modules relevant for the community management tool will be being
tested...of course there may be the odd bug in the core & there can
certainly be UI suggestions which are cross-module. Since our focus
for the weekend will be on this system then all issues relevant to
this system should be logged here (1 place to look)
Post-event we definitely need to again have only 1 place to look, so
either we agree to move the open Trac issues to the Eden instance or
vice versa.
> we can't rely on everyone arriving at time, but I hope that most people
> will (look at the roster). I'm sure that there will still be tasks for those
> who join later.
Yes, I'm sure there will :)
Just want to be sure that those ppl have suitable 'getting started'
materials available rather than the whole focus for that being a
synchronous meeting...
>>> Review - We share what we've done& check where the gaps are.
>> So this is Sunday morning, right?
> See the roster. 2200 Saturday Night.
>> Again, I'm not sure if everyone will be able to attend, but am keen
>> for a core group to do this indeed.
> I'm aware that not everyone will be able to attend,
>> We might need to have more than one of these - I'd be keen for perhaps
>> 2 on Sat& 2 on Sun.
> Really? I guess that these could be quick check-ins. Are you saying 2 in
> total? or 4?
I'm saying 4 - yes I see the need for more frequent quick check-ins of
the core team, which can include 'how's the process going?' not just
'how's the product going?' .
I guess there is also value in a more public wider review & this can
mark a nice break between the focus on building to the focus on
testing/polish.
Although I suspect that Mark (& maybe some others) will be working on
Testing before that though...
F
--
You received this message because you are subscribed to the Google Groups "Sahana-Eden" group.
To post to this group, send email to sahan...@googlegroups.com.
To unsubscribe from this group, send email to sahana-eden...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/sahana-eden?hl=en.
Hi Ashwyn,
Great to see you keen to get started already :)
So this is Row 17.
The proposal that I put forward for this instance was to have a group
per Category & then what is needed for this task would be to provide a
simple UI whereby someone can manage their own group memberships (for
these subscription groups).
Whilst this would work, I'm not actually sure now that this is the
best approach.
We have a 'Saved Search & Subscription' functionality whereby (if the
deployment_setting is enabled) *every* search form includes an option
to Save the search, so that each person can provide a list of
personalised searches on data that interest them. Each of these Saved
Searches can then be Subscribed to by the user so that they can
receive notifications whenever any new record is added to this Search
result set.
Since we have this functionality already, and it's a lot more flexible
than hard-coded groups, then I would propose that we use that for this
functionality.
However, having said that we have it already, as far as I know it
hasn't been tested recently and there have been some significant
changes which may have broken something.
Also, even if it is working, the Usability could well do with
improving (I've not personally tested this end-to-end so am not sure).
So where I'd start is to get a local development environment setup
(Trunk will do just fine) & run through this process - configure the
deployment_settings to enable Saved Searches, configure Email (&
SMS/Twitter too if you like!) & run through the process, including as
a non-Admin user. See if it works, see if is easy/pleasant to use &
report back.
Any UserGuidelines or Selenium Tests (maybe starting with simple IDE)
that you care to develop would be great along the way.
PS I see you've added your name to the list, but you've not yet marked
your expected availability (I know there's no Legend - simply add Grey
to the timeboxes you are likely to manage):
https://docs.google.com/spreadsheet/ccc?key=0AuNG6ihli0CudDFCWXc4MVc5bVk1YnhUUEJGenllMkE#gid=0
Best Wishes,
Fran.
Hi Fran,
Thanks for the info.I ll start with it straight-away. I have added my availability time slots on the list as well.Looking forward to contribute as much as possible.
Regards
-Ashwyn
On 19-Feb-2012 3:28 PM, "Fran Boon" <franc...@gmail.com> wrote:
On 19 February 2012 05:04, ashwyn sharma <ashwy...@gmail.com> wrote:
> I have gone through the ava...
--
You received this message because you are subscribed to the Google Groups "Sahana-Eden" group.
...
Great, well done :)
> However,a few improvements in the UI are certainly required according to me.
> --one of them is that the value of the saved search(i.e. the string that was
> searched for is not visible in the saved searches tab when the user clicks
> on "View and Subscribe to Saved Searches Here"
That would indeed seem pretty useful, if not essential :)
> I am also trying to put up a few selenium tests.It will be great if you
> could give me heads up so as how to approach this from now on.
> I will be ready to discuss all other issues as when and you want me to do
> them.
I suggest that you try to fix the issue you identified & submit a Pull
request on GitHub.
If you'd like to write up a little list of any other issues &
potential solutions then that would be great too :)
Best Wishes,
Fran.
However, I notice that the code
snippet that you have pasted here is going to work only if the module
for which the search is saved is "org".
Also, the text searched and
advanced filters should be there along with the Resource and Module in
the Search Criteria column, as without them the user will not be ableto distinguish between two different search done on the same moduleand resource.