[fossil-users] Painful team interaction with fossil, how to improve?

[Baptiste Daroussin]

Hi,

I'm using fossil for a while now, and I'm quite happy with it, for the scm
part and the web part.

The problem is when going with the ticket part of fossil.

I do not need something sophisticated, the the way the ticket works is ok
with me, however the more the project I'm working on is growing the more
painful it becomes to track ticket activity.

In particular to interact with the submitter. I have found no way to:
1/ send a mail when new ticket is created (yes we can follow via rss feed,
but a mail is way nicer)
2/ send a mail each time to ticket is modified to reporters and followers

(No rss2email is not a solution: not flexible enough)

The 2 above are really painful, and for the first time I really thinking
about migrating from fossil to $something else for the project I do have
the becomes popular :(

The lacks of flexible hooks on server side is also a big problem to me, I
can live with it, but the more I get people involve in the project I'm
working on the more I'm missing it.

What I do need on the hook side is:
1/ send a mail after each "push" of code with a diff:
prior-push-tip/post-push-tip for each branch impacted to a given mailing
list
2/ be able to get access to the diff and run random code on it and reject
the push if not validated

I would like to be able to do the above on top of fossil, how should I do?

regards,
Bapt
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Painful team interaction with fossil, how to improve?

[Ron Wilson]

On Thu, Feb 13, 2014 at 10:24 AM, Baptiste Daroussin <
baptiste.darous...@gmail.com> wrote:

> In particular to interact with the submitter. I have found no way to:
> 1/ send a mail when new ticket is created (yes we can follow via rss feed,
> but a mail is way nicer)
> 2/ send a mail each time to ticket is modified to reporters and followers
>

A ticket hook was added recently. I have not used it, so I don't know how
it it works.


> The lacks of flexible hooks on server side is also a big problem to me
> What I do need on the hook side is:
> 1/ send a mail after each "push" of code with a diff:
> prior-push-tip/post-push-tip for each branch impacted to a given mailing
> list
>

Why not just links to the commits? For example,
http://fossil-scm.org/index.html/info/e327614047 appears to contain the
information you are asking for. This is a lot to put in to an email message.


> 2/ be able to get access to the diff and run random code on it and reject
> the push if not validated
>

Others on this list have set up automatic build servers. I don't think it
would be hard to add validation functionality.

May I ask what version control systems you have used before now?
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Painful team interaction with fossil, how to improve?

[Matt Welland]

On Thu, Feb 13, 2014 at 8:24 AM, Baptiste Daroussin <
baptiste.darous...@gmail.com> wrote:

> Hi,
>
> I'm using fossil for a while now, and I'm quite happy with it, for the scm
> part and the web part.
>
> The problem is when going with the ticket part of fossil.
>
> I do not need something sophisticated, the the way the ticket works is ok
> with me, however the more the project I'm working on is growing the more
> painful it becomes to track ticket activity.
>
> In particular to interact with the submitter. I have found no way to:
> 1/ send a mail when new ticket is created (yes we can follow via rss feed,
> but a mail is way nicer)
> 2/ send a mail each time to ticket is modified to reporters and followers
>
> (No rss2email is not a solution: not flexible enough)
>

I have also found this to be true. Initially I thought that rss would be
sufficient but it turns out to not work well for many people.

I set up the rss2email python script and it has been extremely helpful to
have the email. However I share your opinion that triggers are needed to
make this easy and flexible. There are some triggers available now but I
haven't tried using them yet.


> The 2 above are really painful, and for the first time I really thinking
> about migrating from fossil to $something else for the project I do have
> the becomes popular :(
>
> The lacks of flexible hooks on server side is also a big problem to me, I
> can live with it, but the more I get people involve in the project I'm
> working on the more I'm missing it.
>
> What I do need on the hook side is:
> 1/ send a mail after each "push" of code with a diff:
> prior-push-tip/post-push-tip for each branch impacted to a given mailing
> list
> 2/ be able to get access to the diff and run random code on it and reject
> the push if not validated
>
> I would like to be able to do the above on top of fossil, how should I do?
>

I did a trial set up to achieve something similar to what you describe.
The push was accepted into a clone of the official fossil. The code was
checked out and the regression test run. If the regression ran the code was
then synced to the official fossil. If the regression failed the clone was
deleted and the user informed. I think it worked well but the team wasn't
interested in the extra effort.

To make the above work the official fossil must be pull only of course.


> regards,
> Bapt
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>


-- 
Matt
-=-
90% of the nations wealth is held by 2% of the people. Bummer to be in the
majority...
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Painful team interaction with fossil, how to improve?

[Justin Forest]

Hello.

On Thu, Feb 13, 2014 at 04:24:39PM +0100, Baptiste Daroussin wrote:

In particular to interact with the submitter. I have found no way to:
1/ send a mail when new ticket is created (yes we can follow via rss feed,
but a mail is way nicer)
2/ send a mail each time to ticket is modified to reporters and followers

(No rss2email is not a solution: not flexible enough)


I wrote a Python script that helps myself deal with this.  It looks at 
all tickets and emails all participants with all comments and changes 
since their last reaction.


It also emails users specified in the "responsible" ticket field 
(which you can add in /tktsetup_tab), thus I can assign tickets to 
users and they get emailed without having to comment first.


It also sends all changes to an email address specified in the 
FOSSIL_CC environment variable, for archiving purpose.


I tried using the ticket hooks branch, but found it easier to just 
query the repository every 5 minutes with a cron job (also, this saves 
me from maintaining another web app that would handle the hook 
requests).  I run the script on the same machine that Fossil databases 
are, so there are no performance or load issues.


In case this sounds helpful, you can inspect the script here:



Or download it:



Good luck.


--
Justin Forest
http://umonkey.net/


signature.asc
Description: Digital signature
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Painful team interaction with fossil, how to improve?

[Mark Janssen]

I have used the ticket hooks and they do work. However they will not allow
automatic updates to be sent to whoever logged the ticket.
As a result I have moved the bug tracker to redmine.
On 13 Feb 2014 16:25, "Baptiste Daroussin" 
wrote:

> Hi,
>
> I'm using fossil for a while now, and I'm quite happy with it, for the scm
> part and the web part.
>
> The problem is when going with the ticket part of fossil.
>
> I do not need something sophisticated, the the way the ticket works is ok
> with me, however the more the project I'm working on is growing the more
> painful it becomes to track ticket activity.
>
> In particular to interact with the submitter. I have found no way to:
> 1/ send a mail when new ticket is created (yes we can follow via rss feed,
> but a mail is way nicer)
> 2/ send a mail each time to ticket is modified to reporters and followers
>
> (No rss2email is not a solution: not flexible enough)
>
> The 2 above are really painful, and for the first time I really thinking
> about migrating from fossil to $something else for the project I do have
> the becomes popular :(
>
> The lacks of flexible hooks on server side is also a big problem to me, I
> can live with it, but the more I get people involve in the project I'm
> working on the more I'm missing it.
>
> What I do need on the hook side is:
> 1/ send a mail after each "push" of code with a diff:
> prior-push-tip/post-push-tip for each branch impacted to a given mailing
> list
> 2/ be able to get access to the diff and run random code on it and reject
> the push if not validated
>
> I would like to be able to do the above on top of fossil, how should I do?
>
> regards,
> Bapt
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Painful team interaction with fossil, how to improve?

[Ron Wilson]

On Thu, Feb 13, 2014 at 1:13 PM, Mark Janssen  wrote:

> I have used the ticket hooks and they do work. However they will not allow
> automatic updates to be sent to whoever logged the ticket.
> As a result I have moved the bug tracker to redmine.
>
My impression, from reading comments on this email list, is that the hook
sends the ticket UUID in an HTTP request, then the recipient fetches the
details and forwards some of the details by whatever means.

Assuming that the recipient of the ticket-hook notification is allowed
access to the private_contact field, it could forward the notification to
the ticket originator. Likewise, access to any assigned-to and/or
subscribers fields would also be needed.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Painful team interaction with fossil, how to improve?

[Mark Janssen]

On 13 Feb 2014 19:44, "Ron Wilson"  wrote:
>
> On Thu, Feb 13, 2014 at 1:13 PM, Mark Janssen 
wrote:
>>
>> I have used the ticket hooks and they do work. However they will not
allow automatic updates to be sent to whoever logged the ticket.
>> As a result I have moved the bug tracker to redmine.
>
> My impression, from reading comments on this email list, is that the hook
sends the ticket UUID in an HTTP request, then the recipient fetches the
details and forwards some of the details by whatever means.
>
> Assuming that the recipient of the ticket-hook notification is allowed
access to the private_contact field, it could forward the notification to
the ticket originator. Likewise, access to any assigned-to and/or
subscribers fields would also be needed.
>
>
>

True with effort all of this could be retrieved from the underlying sqlite
db. The reason I didn't do that is that you need opt out and email
verification to prevent sending spam. I could add your email on every
ticket and you would not be able to stop the notifications without admin
interaction. Eventually you are really just rebuilding something like
redmine. I really wanted to make it work, but in the end it just lacks too
many features at the moment.
___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Painful team interaction with fossil, how to improve?

[Ron Wilson]

On Thu, Feb 13, 2014 at 2:46 PM, Mark Janssen  wrote:

> True with effort all of this could be retrieved from the underlying sqlite
> db. The reason I didn't do that is that you need opt out and email
> verification to prevent sending spam. I could add your email on every
> ticket and you would not be able to stop the notifications without admin
> interaction.
>
I had not considered that because, at work, everyone using Fossil is an
employee of the company. For my personal projects,  I don't have to worry
about this. For the OSS projects I contribute to, I either send patch files
or use github. (Mostly I send patch files.)

> Eventually you are really just rebuilding something like redmine. I really
> wanted to make it work, but in the end it just lacks too many features at
> the moment.
>
 I am curious what features are missing.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Painful team interaction with fossil, how to improve?

[Mark Janssen]

On Thu, Feb 13, 2014 at 9:33 PM, Ron Wilson  wrote:

> On Thu, Feb 13, 2014 at 2:46 PM, Mark Janssen wrote:
>
>> True with effort all of this could be retrieved from the underlying
>> sqlite db. The reason I didn't do that is that you need opt out and email
>> verification to prevent sending spam. I could add your email on every
>> ticket and you would not be able to stop the notifications without admin
>> interaction.
>>
> I had not considered that because, at work, everyone using Fossil is an
> employee of the company. For my personal projects,  I don't have to worry
> about this. For the OSS projects I contribute to, I either send patch files
> or use github. (Mostly I send patch files.)
>

Indeed for personal projects and in company projects, what fossil already
offers should suffice.


>  Eventually you are really just rebuilding something like redmine. I
>> really wanted to make it work, but in the end it just lacks too many
>> features at the moment.
>>
>  I am curious what features are missing.
>
>
>
Some things that come to mind:

* Ticket notification for admin, logger and followers (this is the big one).
* Email verification to prevent spam.
* Ability to edit your own comments.

The one thing that fossil gets absolutely right (and most other trackers
don't) is the ability to log issues anonymously without becoming a spam
trap.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Painful team interaction with fossil, how to improve?

[Matt Welland]

I set up our email notification to use a wiki page as the source for email
addresses (creatively named "emailnotification"). Anyone who has read/write
to the wiki can add or remove email addresses. This works fine for us so
far but might not work for a open web facing project.


On Thu, Feb 13, 2014 at 2:06 PM, Mark Janssen  wrote:

>
>
>
> On Thu, Feb 13, 2014 at 9:33 PM, Ron Wilson  wrote:
>
>> On Thu, Feb 13, 2014 at 2:46 PM, Mark Janssen wrote:
>>
>>> True with effort all of this could be retrieved from the underlying
>>> sqlite db. The reason I didn't do that is that you need opt out and email
>>> verification to prevent sending spam. I could add your email on every
>>> ticket and you would not be able to stop the notifications without admin
>>> interaction.
>>>
>> I had not considered that because, at work, everyone using Fossil is an
>> employee of the company. For my personal projects,  I don't have to worry
>> about this. For the OSS projects I contribute to, I either send patch files
>> or use github. (Mostly I send patch files.)
>>
>
> Indeed for personal projects and in company projects, what fossil already
> offers should suffice.
>
>
>>  Eventually you are really just rebuilding something like redmine. I
>>> really wanted to make it work, but in the end it just lacks too many
>>> features at the moment.
>>>
>>  I am curious what features are missing.
>>
>>
>>
> Some things that come to mind:
>
> * Ticket notification for admin, logger and followers (this is the big
> one).
> * Email verification to prevent spam.
> * Ability to edit your own comments.
>
> The one thing that fossil gets absolutely right (and most other trackers
> don't) is the ability to log issues anonymously without becoming a spam
> trap.
>
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>


-- 
Matt
-=-
90% of the nations wealth is held by 2% of the people. Bummer to be in the
majority...
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Painful team interaction with fossil, how to improve?

[Ron Wilson]

On Thu, Feb 13, 2014 at 4:06 PM, Mark Janssen  wrote:

> Some things that come to mind:
>
> * Ticket notification for admin, logger and followers (this is the big
> one).
> * Email verification to prevent spam.
>

I can think of ways of using a list server to mostly handle these 2 items.


> * Ability to edit your own comments.
>

It might be possible to do this by modifying the "edit ticket page".
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Painful team interaction with fossil, how to improve?

[Andy Bradford]

Thus said Mark Janssen on Thu, 13 Feb 2014 22:06:49 +0100:

> * Email verification to prevent spam.

MLMs (mailing list managers; like  ezmlm, mailman, etc...) already solve
this problem.  Perhaps those who  want notifications can subscribe  to a
tic...@domain.dom mailing list and the  ticket hook can send messagse to
the mailing list, instead of individuals.

Andy
-- 
TAI64 timestamp: 400052fd8a40


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Painful team interaction with fossil, how to improve?

[BohwaZ]

Le Thu, 13 Feb 2014 20:44:43 +0400, Justin Forest  a
écrit :

> I wrote a Python script that helps myself deal with this.  It looks
> at all tickets and emails all participants with all comments and
> changes since their last reaction.
> 
> It also emails users specified in the "responsible" ticket field 
> (which you can add in /tktsetup_tab), thus I can assign tickets to 
> users and they get emailed without having to comment first.
> 
> It also sends all changes to an email address specified in the 
> FOSSIL_CC environment variable, for archiving purpose.
> 
> I tried using the ticket hooks branch, but found it easier to just 
> query the repository every 5 minutes with a cron job (also, this
> saves me from maintaining another web app that would handle the hook 
> requests).  I run the script on the same machine that Fossil
> databases are, so there are no performance or load issues.
> 
> In case this sounds helpful, you can inspect the script here:
> 
> 
> 
> Or download it:
> 
> 

That's awesome! Just what I needed. I actually only use the JSON API to
get last tickets edits and send the change to a mailing list, but
sending to ticket participants is what I was looking for, thanks!

-- 
BohwaZ


signature.asc
Description: PGP signature
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Painful team interaction with fossil, how to improve?

[Roy Marples]

Hi

On 13/02/2014 15:24, Baptiste Daroussin wrote:

In particular to interact with the submitter. I have found no way to:

1/ send a mail when new ticket is created (yes we can follow via rss
feed, but a mail is way nicer)


I don't have a huge problem with RSS as it looks to be possible to 
subscribe to all ticket changes which is great for me as a repo admin.

It's also possible subscribe to an individual ticket RSS.

However, using the default skin I don't see an easy way to do this. This 
makes it hard to use.
Would it be possible to add a RSS button to the timeline and the ticket 
pages? Thinking about it, each page could have one and the link is 
filtered based on the filtering for the page.


Roy
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Painful team interaction with fossil, how to improve?

[Roy Marples]

On 18/02/2014 14:40, Roy Marples wrote:

I don't have a huge problem with RSS as it looks to be possible to
subscribe to all ticket changes which is great for me as a repo admin.
It's also possible subscribe to an individual ticket RSS.

However, using the default skin I don't see an easy way to do this.
This makes it hard to use.
Would it be possible to add a RSS button to the timeline and the
ticket pages? Thinking about it, each page could have one and the link
is filtered based on the filtering for the page.


Here is a patch which adds a RSS feed icon after the ticket uuid.
Probably not the best way of doing it, but I couldn't think of another 
way which would allow the user to use a different icon to match their 
skin.


Maybe just "RSS Feed" as a menu item would be better?

Thanks

RoyAdd a RSS feed icon to the ticket view.

--- src/tktsetup.c.orig	2014-02-20 10:23:13.0 +
+++ src/tktsetup.c
@@ -437,13 +437,13 @@ static const char zDefaultView[] =
 @ 
 @ Ticket UUID:
+@ $tkt_uuid
 @ 
 @ if {[hascap s]} {
-@   html "$tkt_uuid "
-@   html "($tkt_id)\n"
-@ } else {
-@   html "$tkt_uuid\n"
+@   html " ($tkt_id)"
 @ }
 @ 
+@  
+@ 
 @ Title:
 @ 
 @ $
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Painful team interaction with fossil, how to improve?

[Ron Wilson]

On Thu, Feb 20, 2014 at 6:56 AM, Roy Marples  wrote:

> Here is a patch which adds a RSS feed icon after the ticket uuid.
> Probably not the best way of doing it, but I couldn't think of another way
> which would allow the user to use a different icon to match their skin.
>
> Maybe just "RSS Feed" as a menu item would be better?
>

>From my experience, the RSS icon is a very common way to provide a way to
subscribe to a feed.

Interesting that you need to make an actual source code change. I would
have expected it could be changed in the header.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Painful team interaction with fossil, how to improve?

[Roy Marples]

On 20/02/2014 15:07, Ron Wilson wrote:

On Thu, Feb 20, 2014 at 6:56 AM, Roy Marples  wrote:


Here is a patch which adds a RSS feed icon after the ticket uuid.
Probably not the best way of doing it, but I couldn't think of
another way which would allow the user to use a different icon to
match their skin.

Maybe just "RSS Feed" as a menu item would be better?


From my experience, the RSS icon is a very common way to provide a way
to subscribe to a feed.

Interesting that you need to make an actual source code change. I
would have expected it could be changed in the header.


The source code change just affects the default HTML for the ticket 
view.
Basically making the default view more useable. You can of course edit 
it in via the www interface.


I wouldn't know how to put it into the header. Maybe some of this tc1 
code to toggle it?


Roy
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users