Introducing Quests: Tailored gamification & bridging in-person events with your community Mike Gitkos Yesterday at 12:39 PM1 day
May 9, 201213 yr Hi all, I just realised that ip.tracker and ip.tickets are different. Is there a way to copy over all of the ip.tracker data to ip.tickets? Or alternatively is thee a way to ipdate the ip.tracker to 3.3.1? OK, now i'm even more confused.... Are there 2 projet, one for tickets and another for tracker or has the tracker been turned into the tickets project? 2 completely different apps. tickets is orientated more towards a support center.
May 9, 201213 yr 2 completely different apps. tickets is orientated more towards a support center. To add to that... It's not 'IP'tickets... It's just 'tickets'... and it's not an IP product...
May 10, 201213 yr yeah, thanks aiwa, i'll try not to step out of line again..... Know your role, son. :-P :-D
May 10, 201213 yr Author Maybe better idea is to publish tracker code in public repository (Git, Hg). For sure community will help in developing by patch queues. That was the idea when they were all community projects too, and it never happened then, so I doubt it's going to change.
May 14, 201213 yr We feel that allowing some trusted developers in the community the opportunity to update and release a new version of IP.Tracker is the best option at present. We have put a lot of thought into this, and as has been mentioned, will be providing more information about the plans in due course. But then that a community thing that was done with a while back no? Unless your bring back the community development again. If it carries the "IP" title why not just bring it on board and develop it like the other applications as it been a major core of many of IP communities.
May 14, 201213 yr But then that a community thing that was done with a while back no? Unless your bring back the community development again. If it carries the "IP" title why not just bring it on board and develop it like the other applications as it been a major core of many of IP communities. manpower? its simple, they saw a problem and took steps to get it corrected. I am glad they have.
May 15, 201213 yr That was the idea when they were all community projects too, and it never happened then, so I doubt it's going to change. But it still never hurts to have it in a place where people can help. ---------- Anyways IPS Why not github? Thats a good place for people to start since you can keep track of whose helping and with the pull requests see exactly what a person has changed. And it's pretty good at merging with existing code(That is once you wrap your head on how to do it properly).
May 15, 201213 yr Why not github? Thats a good place for people to start since you can keep track of whose helping and with the pull requests see exactly what a person has changed. And it's pretty good at merging with existing code(That is once you wrap your head on how to do it properly). I can't speak for IPS by any means, but I think they would prefer a more curated environment where they can ensure quality--and, more to the point, that someone is actually directly responsible for it.
May 15, 201213 yr I can't speak for IPS by any means, but I think they would prefer a more curated environment where they can ensure quality--and, more to the point, that someone is actually directly responsible for it. You can track every change on github (or git rather)https://github.com/L.../commits/masterhttps://github.com/L...e93ea3c990e2d3b Even when you load a file there's a "blame" page for who's responsible for the last change to that line and what commit it came fromhttps://github.com/L...Steam_Login.xml Pull Requests are even more managed since you can communicate with them before it being merged or not.https://github.com/L...n-Method/pull/7
May 15, 201213 yr I would imagine IPS is giving the trusted devs that are working on it guidance so the final product is a cohesive solution that reflects IPS quality. The last thing you want is 100 chunks of code all mangled together by a random DEV that thought it looked good that day.
May 15, 201213 yr The last thing you want is 100 chunks of code all mangled together by a random DEV that thought it looked good that day. I might prefer that to Matt Mecham. :P
May 15, 201213 yr I would imagine IPS is giving the trusted devs that are working on it guidance so the final product is a cohesive solution that reflects IPS quality. The last thing you want is 100 chunks of code all mangled together by a random DEV that thought it looked good that day. Pretty much, I put the team of developers together based on their skills and code quality. I think we've got a pretty good team! P.S., You'll know more when we release 2.1.0.
May 17, 201213 yr Generate report list for issues fixed in... cannot generate for IP.Board 3.3.3 version
May 17, 201213 yr Generate report list for issues fixed in... cannot generate for IP.Board 3.3.3 versionIt's a developer only version at the moment, so you can't select it.
May 20, 201213 yr It's a developer only version at the moment, so you can't select it. and this is bad - we want to know what was actually done in developer version before release
May 21, 201213 yr and this is bad - we want to know what was actually done in developer version before release This really has nothing to do with this topic. That was simply how the version was configured when it was set up, not something to do with the software itself. I've made it opened to the public.
May 23, 201213 yr Just a quick question to the new devs: How long (you think) you/the team will need to fix all open bugs? We still have at this moment 50x General, 2x Skin, 12x Minimal and 10x Unconfirmed open tracker entrys and (for now with a team of 5 devs) it does not done much at the tracker... I had hoped for more from the "new team"...
May 23, 201213 yr Management Just a quick question to the new devs: How long (you think) you/the team will need to fix all open bugs? We still have at this moment 50x General, 2x Skin, 12x Minimal and 10x Unconfirmed open tracker entrys and (for now with a team of 5 devs) it does not done much at the tracker... I had hoped for more from the "new team"... I think it a touch inappropriate to post something like that directed to people volunteering to make something.
May 23, 201213 yr Just a quick question to the new devs: How long (you think) you/the team will need to fix all open bugs? We still have at this moment 50x General, 2x Skin, 12x Minimal and 10x Unconfirmed open tracker entrys and (for now with a team of 5 devs) it does not done much at the tracker... I had hoped for more from the "new team"... We've also fixed over 20 bugs so far and confirmed/investigated countless bug reports, which isn't bad going. Many of the team have been studying hard for exams to further their own careers. Please also remember that Tracker is a rather complex system behind the scenes.
May 23, 201213 yr Please also remember that Tracker is a rather complex system behind the scenes. To say the least. :ermm:
May 23, 201213 yr ... I had hoped for more from the "new team"... as a developer, I have to say you, better if you dedicate to other things that come in here to say foolish things. :mad:
May 24, 201213 yr I had hoped for more from the "new team"... We have only recently had confirmation that IP.Tracker is back in development. You should be happy about that for now. :)
Archived
This topic is now archived and is closed to further replies.