allura-vm2

[Chris Lambertus]

Hi allura,

While troubleshooting some high disk usage on our VM hosts, I noticed that 
allura-vm2 is heavily into swap. I’ve doubled the ram capacity from 4->8GB but 
I need to reboot the machine for this to take effect. Since this is impacting 
performance on other VMs, I need to do this restart ASAP. If there is anything 
you need to shut down on the VM please do so within the hour, otherwise I will 
be restarting the VM at 0320 UTC.

Thanks,
Chris
ASF Infra



signature.asc
Description: Message signed with OpenPGP

Re: allura-vm2

[Chris Lambertus]

Your VM has been rebooted and the memory allocation increased. I have commented 
out your /swapfile. DO NOT add disk-based swap to your VM again. Contact Infra 
if you need additional resources.

-Chris



> On Apr 25, 2018, at 7:20 PM, Chris Lambertus  wrote:
> 
> Hi allura,
> 
> While troubleshooting some high disk usage on our VM hosts, I noticed that 
> allura-vm2 is heavily into swap. I’ve doubled the ram capacity from 4->8GB 
> but I need to reboot the machine for this to take effect. Since this is 
> impacting performance on other VMs, I need to do this restart ASAP. If there 
> is anything you need to shut down on the VM please do so within the hour, 
> otherwise I will be restarting the VM at 0320 UTC.
> 
> Thanks,
> Chris
> ASF Infra
> 



signature.asc
Description: Message signed with OpenPGP

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

[Deshani Geethika]

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 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 Allura team.
> >
> > Could you guide me what would be the best way to start off with.
> >
> > Regards!
> >
>
> Sounds like good goals for the community bonding period.
>
> I've added you as a developer on our self-hosted Allura project
> https://forge-allura.apache.org/p/allura/ which means you can assign
> tickets to
> yourself, make new ones, update existing ones, etc.  I'd recommend having
> many
> small incremental tickets (perhaps even smaller pieces of work than you
> outlined
> in the project proposal), so that its easy to manage them and review
> them.  And
> of course you don't need to make them all right away :)
>
> To familiarize yourself with Allura, you can read more of the
> documentation -
> assuming you haven't read it all already ;)  https://forge-allura.apache.
> org/docs/
>
> And working on Allura code itself is best.  Find an existing ticket or
> anything
> you notice that could be made better, and make a fix for it.  A really
> easy one
> that I could suggest is https://forge-allura.apache.
> org/p/allura/tickets/1699/
>
> I've also noticed that our test suite has failed the past few times:
> https://builds.apache.org/blue/organizations/jenkins/Allura/activity  It
> probably is related to the "Make debug pages and post permalinks work
> correctly
> when behind a proxy" commit.  You could take a look at fixing that if you
> want.
> Otherwise I will soon.
>
> Lastly, reviewing other people's work is a good way to get familiar with
> the
> code and best practices.  I will have a fix for
> https://forge-allura.apache.org/p/allura/tickets/6353/ coming soon, so
> watch out
> for that.  You won't be able to merge my branch to master, but it can be a
> good
> way for you to learn from others.  And any constructive feedback would be
> welcome too, of course.
>
>
>
>
> --
> Dave Brondsema : d...@brondsema.net
> http://www.brondsema.net : personal
> http://www.splike.com : programming
>   <><
>



-- 
*Deshani Geethika*
Undergraduate at Department of Computer Science and Engineering
Faculty of Engineering - University of Moratuwa Sri Lanka
LinkedIn  | GitHub
 | Mobile - +94776383034

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

[Dave Brondsema]

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 like to get more familiarized
> with Allura code-base and Allura team.
> 
> Could you guide me what would be the best way to start off with.
> 
> Regards!
> 

Sounds like good goals for the community bonding period.

I've added you as a developer on our self-hosted Allura project
https://forge-allura.apache.org/p/allura/ which means you can assign tickets to
yourself, make new ones, update existing ones, etc.  I'd recommend having many
small incremental tickets (perhaps even smaller pieces of work than you outlined
in the project proposal), so that its easy to manage them and review them.  And
of course you don't need to make them all right away :)

To familiarize yourself with Allura, you can read more of the documentation -
assuming you haven't read it all already ;)  
https://forge-allura.apache.org/docs/

And working on Allura code itself is best.  Find an existing ticket or anything
you notice that could be made better, and make a fix for it.  A really easy one
that I could suggest is https://forge-allura.apache.org/p/allura/tickets/1699/

I've also noticed that our test suite has failed the past few times:
https://builds.apache.org/blue/organizations/jenkins/Allura/activity  It
probably is related to the "Make debug pages and post permalinks work correctly
when behind a proxy" commit.  You could take a look at fixing that if you want.
Otherwise I will soon.

Lastly, reviewing other people's work is a good way to get familiar with the
code and best practices.  I will have a fix for
https://forge-allura.apache.org/p/allura/tickets/6353/ coming soon, so watch out
for that.  You won't be able to merge my branch to master, but it can be a good
way for you to learn from others.  And any constructive feedback would be
welcome too, of course.




-- 
Dave Brondsema : d...@brondsema.net
http://www.brondsema.net : personal
http://www.splike.com : programming
  <><

[allura:tickets] #6353 Pre-fill "private" using URL param

[Dave Brondsema]

---

** [tickets:#6353] Pre-fill "private" using URL param**

**Status:** review
**Milestone:** unreleased
**Labels:** bitesize for-support 
**Created:** Mon Jun 10, 2013 06:13 PM UTC by Chris Tsai
**Last Updated:** Tue Mar 31, 2015 05:31 PM UTC
**Owner:** Dave Brondsema


Something like https://sourceforge.net/p/forge/site-support/new/?private=true 
to pre-check the "private" checkbox would be especially nice on pages that ask 
for tickets for items like security vulnerabilities or anything else that might 
involve private data.


---

Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed 
to https://forge-allura.apache.org/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://forge-allura.apache.org/p/allura/admin/tickets/options.  Or, if this is 
a mailing list, you can unsubscribe from the mailing list.

[allura:tickets] Ticket 6353 discussion

[Dave Brondsema]

- **status**: open --> review
- **assigned_to**: Dave Brondsema
- **Comment**:

Done on branch db/6353



---

** [tickets:#6353] Pre-fill "private" using URL param**

**Status:** review
**Milestone:** unreleased
**Labels:** bitesize for-support 
**Created:** Mon Jun 10, 2013 06:13 PM UTC by Chris Tsai
**Last Updated:** Tue Mar 31, 2015 05:31 PM UTC
**Owner:** Dave Brondsema


Something like https://sourceforge.net/p/forge/site-support/new/?private=true 
to pre-check the "private" checkbox would be especially nice on pages that ask 
for tickets for items like security vulnerabilities or anything else that might 
involve private data.


---

Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed 
to https://forge-allura.apache.org/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://forge-allura.apache.org/p/allura/admin/tickets/options.  Or, if this is 
a mailing list, you can unsubscribe from the mailing list.