I know Patch-tag is on the back burner, but hopefully this one wouldn't be too hard. Could the home page redirect to the HTTPS site? The reason I ask is because the login form posts to http://..., so unless you explicitly visit https://patch-tag.com/ in the first place, your password is sent in the clear
1) I am going to be moving patch-tag's bug tracking mechanism (such as it is) from patch-tag gitit repo to google hosting, which I think will work better.
2) As one of the more active users, I wonder if you would be interested in being a patch-tag "gold team member" or some such thing (I just made up the name) where you would be somewhat privileged to file and prioritize bug requests, contribute documentation and other things like that as time goes on. I realize I haven't been giving patch tag the attention it needs and am thinking of driving things in an even more communitarian direction. (ram, cc'd, will probably be helping with this as well.
If this is interesting to you let me know and we can explore some ideas.
On Tue, Sep 6, 2011 at 9:21 AM, Ash Moran <ash.mo...@patchspace.co.uk> wrote: > Hi
> I know Patch-tag is on the back burner, but hopefully this one wouldn't be too hard. Could the home page redirect to the HTTPS site? The reason I ask is because the login form posts to http://..., so unless you explicitly visit https://patch-tag.com/ in the first place, your password is sent in the clear
> -- > You received this message because you are subscribed to the Google Groups "patch-tag-users" group. > To post to this group, send email to patch-tag-users@googlegroups.com. > To unsubscribe from this group, send email to patch-tag-users+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/patch-tag-users?hl=en.
-- -- _____________________ Thomas Hartman MarketPsych LLC MarketPsy Capital LLC 2400 Broadway, Suite 220 Santa Monica, CA, USA Tel: +1.310.573.8523 ______________________
This e-mail message and any attachments may contain information that is confidential, proprietary or privileged, and is for the named person’s use only. No confidentiality or privilege is waived or lost by any mistransmission. If you are not the intended recipient or agent responsible for delivering it to the intended recipient, you are hereby notified that any dissemination, distribution, copying or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify us immediately and destroy all copies of this message and attachments without disclosing the contents to anyone. Neither this message nor any information included herein constitute an offer to sell or the solicitation of an offer to buy any securities or investment product, or legal, tax, accounting, or investment advice.
> 1) I am going to be moving patch-tag's bug tracking mechanism (such as > it is) from patch-tag gitit repo to google hosting, which I think will > work better.
Hi Thomas, Ram
Sure, that sounds like a good idea.
> 2) As one of the more active users, I wonder if you would be > interested in being a patch-tag "gold team member" or some such thing > (I just made up the name) where you would be somewhat privileged to > file and prioritize bug requests, contribute documentation and other > things like that as time goes on. I realize I haven't been giving > patch tag the attention it needs and am thinking of driving things in > an even more communitarian direction. (ram, cc'd, will probably be > helping with this as well.
I'd be happy to be on the team so the option is there for me to help out if I can, but I must warn you I can't commit to actively help out on a regular basis. I'm wary of spreading my time too thin, as if I get busy with work I ends up doing nothing well. (I've made that mistake before.)
