Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Nice - with this merged it seems like a good spot to do a release of Allura. I will get that started soon, probably tomorrow. On 9/18/18 3:14 AM, Deshani Geethika wrote: > Thanks a lot. I've changed the entry point name into "activity" and added a > merge request ( >

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

I added some logging to SectionsUtil.load_sections to see what it was getting from the config, and other variables. Looks like the problem is that the section name (entry point name) is "followers" so that needs to be used. On 9/16/18 2:37 PM, Deshani Geethika wrote: > Hi Dave, > > To move up

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Hi Dave, To move up the activity section in dashboard and profile I've modified the development.ini file. For the user profile, the section order was there but commented, so that I've uncommented the line. For the dashboard section order, I've added a similar line, but it doesn't work. (activity

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Hi! I've merged that merge request, it looks good. I think the title text is ok. The layout of the logo runs into the main gray content though. It'd be nice if it had a bit of space like it does on the user profile page, for example. I see on the user profile page there is an empty that helps

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Hi Dave, Sorry for the delays. I've done some fixes on dashboard styles and added a merge request ( https://forge-allura.apache.org/p/allura/git/merge-requests/271/) Please review it and let me know if any improvements required. Also, for the dashboard title, currently it is shown as *username /

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Thanks a lot. Will try these and let you know On Fri, Jul 27, 2018 at 8:52 PM Dave Brondsema wrote: > Sure, here's some thoughts: > > Inheriting from TestGitRepo means it gets all the test_* functions, so > when I > ran nosetests, it ran a lot of TestGitRepo.test_* tests too, which we > don't

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Sure, here's some thoughts: Inheriting from TestGitRepo means it gets all the test_* functions, so when I ran nosetests, it ran a lot of TestGitRepo.test_* tests too, which we don't want to happen. So I'd remove that inheritance. You probably will have to duplicate the setup_with_tools()

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Hi Dave, I have started to write a test case for Merge Requests Section. For that I have followed ForgeGit tests but it doesn't work for me. I was trying to create a merge request and see whether it appears in dashboard. I've pushed the code into my fork

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Hi Dave, Thank you for sharing these valuable information. I have added a merge request . Please review it and let me know any further improvements. Regards! On Mon, Jul 16, 2018 at 9:54 PM Dave Brondsema wrote: > On 7/16/18

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Hi Dave, I have tried with adding above lines, but still doesn't work. Can you take a look at my implementation ? Thanks! On Fri, Jul 13, 2018 at 7:31 PM Dave Brondsema wrote: >

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

My first thought is that it probably is not getting indexed in solr. That runs in a background task, so during tests it won't happen automatically. Try adding this: ThreadLocalORMSession.flush_all() M.MonQTask.run_ready() ThreadLocalORMSession.flush_all() The

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Hi Dave, I have started to create a test case for Tickets Section. I was trying to create a new ticket and check whether it appears in Dashboard, but it doesn't work. It seems like I've done something wrong when creating new ticket. Could you kindly take a look at my implementation

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Hi Dave, I've created a test case for Dashboard sections and added a merge request . Please review it and let me know if any improvements required. Also, could you let me know what are the other functionalities should be tested in

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Hi Dave, I've started to work on Followers Section and pushed the current code to my fork. (https://forge-allura.apache.org/u/deshani/allura-personal-dashboard/ci/6522ff400387f1b1143d27cdd3afd1a63a811785/ ) I need to create activity_app instance in class FollowersSection in

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Hi Dave, I've modified the paged_search method and now it is working for dashboard too. But I have some confusions how to call this method to load tickets to UI. Could you help me to sort this out? Regards! On Fri, Jun 22, 2018 at 8:08 AM Deshani Geethika wrote: > Thanks a lot. Will give a

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Thanks a lot. Will give a try and let you know On Thu, Jun 21, 2018 at 11:36 PM Dave Brondsema wrote: > Sounds good, pagination is definitely important if people have a lot of > tickets. > In the ForgeTracker tool forgetracker/model/ticket.py there are methods > paged_search() and

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Sounds good, pagination is definitely important if people have a lot of tickets. In the ForgeTracker tool forgetracker/model/ticket.py there are methods paged_search() and paged_query() which might be good reference points. It looks like they probably can't be re-used directly, since they expect

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Hi Dave, Currently I'm working on creating "Tickets Section" of Dashboard. I have implemented to load all of the tickets at once, but I thought to paginate this and I'm working on it. Will give you an update soon. If you have any suggestions please let me know. Regards! On Thu, Jun 14, 2018 at

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Hi Dave, Thanks for reviewing and merging the above requests. I've created a helper method to avoid code duplication in DashboardController.index and UserProfileApp.profile_sections, and added a merge request . Please review it

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Hi Dave, I've updated the above merge request , as I've fixed an issue in a template. Meanwhile, I started a new branch for dashboard tests and added a simple test to check '/dashboard' route. I've created a new merge request

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

On 6/6/18 5:37 AM, Deshani Geethika wrote: > Hi Dave, > > I need some help in understanding an error related to test cases. > > I was trying to write a test case to check the '/neighborhood' route in > Allura/allura/tests/functional/test_root.py as below. > > def test_neighborhood(self): >>

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Hi Dave, I need some help in understanding an error related to test cases. I was trying to write a test case to check the '/neighborhood' route in Allura/allura/tests/functional/test_root.py as below. def test_neighborhood(self): > response = self.app.get('/neighborhood/') But I

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Hi Dave, I've added the first merge request for Personal Dashboard. Please review it and let me know any improvements. Merge Request: https://forge-allura.apache.org/p/allura/git/merge-requests/255/ Regards! On Wed, May 30, 2018 at 12:14 AM Dave Brondsema wrote: > On 5/28/18 4:12 AM, Deshani

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

On 5/28/18 4:12 AM, Deshani Geethika wrote: > Hi Dave, > > During last week I focused on learning frameworks and basics related to > Allura and now I’m ready to add the first merge request of Personal > Dashboard. When adding the merge request, should it be added to the master > branch of the

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Hi Dave, During last week I focused on learning frameworks and basics related to Allura and now I’m ready to add the first merge request of Personal Dashboard. When adding the merge request, should it be added to the master branch of the remote? Regards! On Fri, May 18, 2018 at 6:41 AM Dave

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

That works, and so does google hangouts. See you then On 5/17/18 2:17 PM, Deshani Geethika wrote: > Thanks. Can we make it tomorrow (18th May) 10am ET? or any other convenient > time of your choice. > > Is it a Hangouts call? or please let me know if I need to setup any other > application > >

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Thanks. Can we make it tomorrow (18th May) 10am ET? or any other convenient time of your choice. Is it a Hangouts call? or please let me know if I need to setup any other application Regards! On Thu, May 17, 2018 at 8:57 PM, Dave Brondsema wrote: > Sure. I am available

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Sure. I am available 10am-6pm ET on weekdays, and also Sat/Sun could be available 12pm - 10pm. https://www.timeanddate.com/worldclock/converter.html?p1=tz_ist=tz_et On 5/17/18 7:10 AM, Deshani Geethika wrote: > Hi Dave, > > To get an overview about Allura code-base and conventions, it would be

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Hi Dave, To get an overview about Allura code-base and conventions, it would be great if we can arrange a call. Could you tell me your available time slots for a meeting. My time zone is IST (+0530). Regards! On Mon, May 14, 2018 at 9:44 PM, Dave Brondsema wrote: > Hi, > >

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Hi, Allura can be pretty flexible, but in general we follow these conventions: Core components that are deeply integrated into allura go in the Allura/allura/model & controllers directories. Non-essential components go in the Allura/allura/ext/ directory. Like "extra" or "extensions". So this

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Hi Dave, During last few days I was working on my GSoC project and I have few problems to be clarified. In my proposal I have mentioned that, personal_dashboard folder should be created on the path

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

On 5/2/18 11:24 AM, Deshani Geethika wrote: > Hi Dave, > > Thanks for the information. I have few questions to be clarified. > > I think replacing spaces with underscores would be a good way to do it, > since on many wikis they are > interchangable. (They aren't for allura, but we could move

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Hi Dave, Thanks for the information. I have few questions to be clarified. I think replacing spaces with underscores would be a good way to do it, since on many wikis they are interchangable. (They aren't for allura, but we could move towards that). Here do you mean that spaces and underscores

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Cool. That email_address property should be the main one and changing it should reflect in the outgoing emails that are sent to subscribers after commenting or editing a wiki page. Allura also supports *inbound* emails on most artifacts including wiki pages. So someone could reply to the wiki

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Hi all, During last few days, I spent time on reading the Allura documentation and on getting familiarized with Allura codebase. Then, I have started to work on the ticket - #1699 Fix incoming email for wiki pages with space in the title .

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

Hi Dave, Thanks for the detailed explanation. I will start working on this and come back to you with my progress Regards! On Wed, Apr 25, 2018 at 9:55 PM, Dave Brondsema wrote: > On 4/24/18 11:14 AM, Deshani Geethika wrote: > > Hi Dave, > > > > As per GSoC official

Re: [GSoC] [COMDEV-254] Allura - Personal Dashboard

On 4/24/18 11:14 AM, Deshani Geethika wrote: > Hi Dave, > > As per GSoC official time-line, from 23rd April to 14th May period is > considered as "Community Bonding Period". > > During this period I would like to finalize my design and separate my > project into several tickets. Also, I would

[GSoC] [COMDEV-254] Allura - Personal Dashboard

Hi Dave, As per GSoC official time-line, from 23rd April to 14th May period is considered as "Community Bonding Period". During this period I would like to finalize my design and separate my project into several tickets. Also, I would like to get more familiarized with Allura code-base and