[Swift-devel] Planning next set of Swift features and releases

[Michael Wilde]

We have, minimally, a funded and still unmet charter from CNARI to do 
real provenance and get it in use in HNL.

And we have a live and growing user group in OOPS who can benefit from 
provenance as I stated on the list in the past week or two. (and who in 
fact has built a simple web interface to view swift results)

On 4/22/09 8:51 AM, Ian Foster wrote:
> If no-one is using these things, then perhaps we should not be doing them.

No one can use them till they exist.

> I myself think they are really important, and so hope that we would 
> instead get people to use them. But if Mike can't get people to use 
> them, then maybe we decide they are unimportant.

See above.

> On Apr 22, 2009, at 4:55 AM, Ben Clifford wrote:
> 
>>> Provenance
>>>
>>> - make it end-user useful and ready
>>> - easy to get perf numbers
>>> - easy to associate swift parameters with files and runs
>>
>> yes.
>>
>> (the rest of this paragraph is a rant) I am fairly happy with the ongoing
>> development of this at the moment for PC3. However, there has been a
>> consistent lack of feedback for the provenance work. I attribute no blame
>> on any person for this, but it is the case that no on aside from Luiz has
>> spent a significant amount of time working with the provenance code over
>> the 16 months that it has been in the SVN. People throw in plenty of
>> feature requests, some of which already exist, and then make no use of
>> them. If other people in the group do not test out features in the
>> provenance code properly (i.e. more than spending one hour every month)
>> then people cannot complain when the features do not work how they want.
>> The same applies to the log processing graphs - people need to come up
>> with concrete technical criticisms rather than vague "please make it
>> better"
>